search for: c4t0d0s0

...ksums). However, I am not certain how to correctly extract such ganged blocks: 3.1) Trying the first DVA as-is fails (how does it know the "correct" power-of-two size for a direct request of on-VDEV data?): # zdb -R rpool 0:191e70400:20200:r > /tmp/rp1 Found vdev: /dev/dsk/c4t0d0s0 Assertion failed: size <= (1ULL << 17) (0x20200 <= 0x20000), file ../../../uts/common/fs/zfs/zio.c, line 493 Abort 3.2) Disabling assertions seems to help: # zdb -AAA -R rpool 0:191e70400:20200:r > /tmp/rp3 Found vdev: /dev/dsk/c4t0d0s0 Comparing RP1 and RP3 files showed that the...

I''m using zfs not to have access to a fail-safe backed up system, but to easily manage my file system. I would like to be able to, as I buy new harddrives, just to be able to replace the old ones. I''m very environmentally concious, so I don''t want to leave old drives in there to consume power as they''ve already been replaced by larger ones. However, ZFS

...9;'. Once this is done, the pool will no longer be accessible on older software versions. scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c4t0d0s0 ONLINE 0 0 0 c4t1d0s0 ONLINE 0 0 0 c9t0d0s0 ONLINE 0 0 0 c9t2d0s0 ONLINE 0 0 0 errors: No known data errors Once I decide that these -- David Dyer-Bennet, dd-b at dd-b.net; http://dd-b.net/ Snapsh...

...import pool: space id: 123931456072276617 state: FAULTED status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see: http://www.sun.com/msg/ZFS-8000-5E config: space UNAVAIL insufficient replicas c4t0d0s0 UNAVAIL corrupted data and the disk is reported ''unknown'' by format. Anyone seen something simular? The pool is still version 6, since I''d like to use it on standard Leopard which has the read-only zfs limited to version 6. Could a cure be to upgrade (OS and/or zfs...

...39; or replace the device with ''zpool replace''. see: http://www.sun.com/msg/ZFS-8000-9P scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c4t0d0s0 ONLINE 0 0 0 c4t1d0s0 ONLINE 0 0 2 errors: No known data errors This is the version of the ARECA driver that comes with Opensolaris. root at yoda:~/bin# pkginfo -l SUNWarcmsr PKGINST: SUNWarcmsr NAME: Areca SAS/SATA RAID driver CATEGORY: sy...

...some features are unavailable. action: Upgrade the pool using ''zpool upgrade''. Once this is done, the pool will no longer be accessible on older software versions. scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 c4t0d0s0 ONLINE 0 0 0 errors: No known data errors root at haggis:/mnt# echo | format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <DEFAULT cyl 28468 alt 2 hd 255 sec 63> /pci at 0,0/pci103c,30c5 at 1f,2/disk at 0,0 Specify disk (enter its number...

Hi, I have the following partions on my laptop, Inspiron 6000, from fdisk: 1 Other OS 0 11 12 0 2 EXT LBA 12 2561 2550 26 3 Active Solaris2 2562 9728 7167 74 First one is for Dell utilities. Second one is NTFS and the third is ZFS. I am currently using OpenSolaris 2009.06

I have a desktop system with 2 ZFS mirrors. One drive in one mirror is starting to produce read errors and slowing things down dramatically. I detached it and the system is running fine. I can''t tell which drive it is though! The error message and format command let me know which pair the bad drive is in, but I don''t know how to get any more info than that like the serial number

...grades or if/when one of the disks fails? I''ve tried the procedure in VMware and found a few gotchas, but nothing too serious (like "zpool import -f rpool" to make grub work after installation, and trying to create the second zpool on c4t0d0p1 -- which happened to be the same as c4t0d0s0, where rpool lives -- instead of c4t0d0p2; funny "zpool create" didn''t complain?) 3) One problem I don''t understand why I got is this: When I attach a new virgin disk to the system, I first run format->fdisk to make two fdisk partitions and then use prtvtoc/fmthard t...

...don''t really know how to interpret what I see. I did check the vdev_path with " fmdump -eV | grep vdev_path | sort | uniq -c" to see if it was only certain disks, but every disk in the array is listed in the file, albeit with different frequencies: 2189 vdev_path = /dev/dsk/c4t0d0s0 1077 vdev_path = /dev/dsk/c4t0d1s0 1077 vdev_path = /dev/dsk/c4t0d2s0 1097 vdev_path = /dev/dsk/c4t0d3s0 25 vdev_path = /dev/dsk/c4t0d4s0 25 vdev_path = /dev/dsk/c4t0d5s0 20 vdev_path = /dev/dsk/c4t0d6s0 1072 vdev_path = /dev/dsk/c4t0d7s0 1092 vdev_path = /dev/dsk/c4t1...