search for: resilvered

...-8000-9P scrub: resilver in progress for 0h0m, 0.00% done, 57h3m to go config: NAME STATE READ WRITE CKSUM rc-pool DEGRADED 0 0 0 mirror DEGRADED 0 0 0 c4t1d0 ONLINE 0 0 0 5.56M resilvered replacing DEGRADED 0 0 0 c4t2d0s0/o FAULTED 1.71M 23.3M 0 too many errors c4t2d0 ONLINE 0 0 0 5.43M resilvered c5t1d0 ONLINE 0 0 0 5.55M resilvered And a few minutes later: # zpo...

...a large number of problematic disks due to a bad production batch, leading me to resilver quite a few times, progressively replacing each disk as it dies (and now preemptively removing disks.) My complaint is that resilvering ends up taking... days! The average write rate to the disk being resilvered is 1 to 3 MB/sec. You can see zpool status and iostat -v output here: http://pastebin.com/mcbb8dfd When I read files off the zpool, I get quite a few MB/sec even in a degraded state, although the zpool is idle while resilvering in this case - no snapshots or anything happening on it. The syst...

Hello, I''m working with someone who replaced a failed 1TB drive (50% utilized), on an X4540 running OS build 134, and I think something must be wrong. Last Tuesday afternoon, zpool status reported: scrub: resilver in progress for 306h0m, 63.87% done, 173h7m to go and a week being 168 hours, that put completion at sometime tomorrow night. However, he just reported zpool status shows:

Hi all I''m seeing some rather bad resilver times for a pool of WD Green drives (I know, bad drives, but leave that). Does resilver go through the whole pool or just the VDEV in question? -- Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 roy at karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres

The default blocksize is 128K. If you are using mirrors, then each block on disk will be 128K whenever possible. But if you''re using raidzN with a capacity of M disks (M disks useful capacity + N disks redundancy) then the block size on each individual disk will be 128K / M. Right? This is one of the reasons the raidzN resilver code is inefficient. Since you end up waiting for the

So, when you add a log device to a pool, it initiates a resilver. What is it actually doing, though? Isn''t the slog a copy of the in-memory intent log? Wouldn''t it just simply replicate the data that''s in the other log, checked against what''s in RAM? And presumably there isn''t that much data in the slog so there isn''t that much to check? Or

Hello All I read this thread Resilver/scrub times? for a few minutes and I have recognize that I dont know the different between Resilvering and Scrubing. Shame on me. :-( I dont find some declarations in the man-pages and I know the command to start scrubing "zpool scrub tank" but what is the command to start resilver and what is the different? -- Best Regards Alexander Dezember, 20

Is there any way to control the resliver speed? Having attached a third disk to a mirror (so I can replace the other disks with larger ones) the resilver goes at a fraction of the speed of the same operation using disk suite. However it still renders the system pretty much unusable for anything else. So I would like to control the rate of the resilver. Either slow it down a lot so that the

...see: http://www.sun.com/msg/ZFS-8000-9P scrub: resilver completed after 4h9m with 0 errors on Mon Apr 12 18:12:26 2010 config: NAME STATE READ WRITE CKSUM sasuc8i ONLINE 0 0 0 raidz2 ONLINE 0 0 0 c12t4d0 ONLINE 0 0 5 108K resilvered c12t8d0 ONLINE 0 0 0 254G resilvered c12t6d0 ONLINE 0 0 0 c12t7d0 ONLINE 0 0 0 c12t0d0 ONLINE 0 0 1 21.5K resilvered c12t1d0 ONLINE 0 0 2 43K resilvered c12t2d0 ONLINE 0 0 4 8...

Hi list, Here''s my case : pool: mypool state: DEGRADED status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scrub: resilver in progress for 147h19m, 100.00% done, 0h0m to go config: NAME STATE READ WRITE CKSUM filerbackup13 DEGRADED 0 0 0...

...c6t17d0 ONLINE 0 0 0 c6t18d0 ONLINE 0 0 0 c6t19d0 ONLINE 0 0 0 c6t20d0 ONLINE 0 0 0 c6t21d0 ONLINE 0 0 0 c6t22d0 ONLINE 0 0 0 592M resilvered c6t23d0 ONLINE 0 0 0 c6t24d0 ONLINE 0 0 0 c6t46d0 ONLINE 0 0 0 c6t47d0 ONLINE 0 0 0 c6t25d0 ONLINE 0 0 0 c6t26d0 ONLINE 0 0 0...

This past weekend, but holiday was ruined due to a log device "replacement" gone awry. I posted all about it here: http://jmlittle.blogspot.com/2008/05/problem-with-slogs-how-i-lost.html In a nutshell, an resilver of a single log device with itself, due to the fact one can''t remove a log device from a pool once defined, cause ZFS to fully resilver but then attach the log

I have a situation where my zpool (with two radiz2s) is resilvering and reaches a certain point, then starts over. There no read, write or checksum errors. The disks do have a fair amount of resilvering to do, as I''ve had a variety of disk failures. But at the core of things, there''s enough parity data to avoid data loss, and the zpool is functioning fine, albeit in a

In a discussion a few weeks back, it was mentioned that the Best Practices Guide says something like "Don''t put more than ___ disks into a single vdev." At first, I challenged this idea, because I see no reason why a 21-disk raidz3 would be bad. It seems like a good thing. I was operating on assumption that resilver time was limited by sustainable throughput of disks, which

I''ve got a Thumper running snv_57 and a large ZFS pool. I recently noticed a drive throwing some read errors, so I did the right thing and zfs replaced it with a spare. Everything went well, but the resilvering process seems to be taking an eternity: # zpool status pool: bigpool state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was

...ice is gone Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci@0 ,0/pci8086,340e@7/pci1028,1f15@0/sd@26,0 (sd46): Mar 22 21:47:55 solaris Command failed to complete...Device is gone # zpool status -v pool: test state: DEGRADED status: One or more devices is currently being resilvered. The pool will continue to function in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Wed Mar 20 19:13:40 2013 27.4T scanned out of 69.6T at 183M/s, 67h11m to go 2.43T resilvered, 39.32% done config: NAME...

...2 15:41:50 2010 config: NAME STATE READ WRITE CKSUM zroot DEGRADED 18 0 0 mirror DEGRADED 44 0 23 c1t1d0s2 DEGRADED 74 0 23 too many errors c1t0d0s2 ONLINE 0 0 67 29.8G resilvered errors: Permanent errors have been detected in the following files: zroot/packages:<0xad58> zroot/packages:<0x11477> zroot/packages:<0x2531d> <0x6e>:<0xc0f2> <0x6e>:<0xce68> <0x6e>:<0x28d9f&gt...

...g report if necessary. In scenario where is say three raidz2 groups consisting several disks, two disks fail in different raidz-groups. You have degraded pool and two degraded raidz2 groups. Now, one replaces first disk and starts resilvering, it takes day, two days, three days, counter says 100% resilvered but new data is still written to disk being replaced, counter SHOULD update if data amount increases in group. Before that first disk is resilvered, second failed disk in second group is replaced resulting in BOTH resilver-processes start from beginning making pool rather unusable due two resilvers...

hi, i have raid1 on zfs with 2 device on pool first device died and boot from second not working... i try to get http://mfsbsd.vx.sk/ flash and load from it with zpool import http://puu.sh/2402E when i load zfs.ko and opensolaris.ko i see this message: Solaris: WARNING: Can''t open objset for zroot/var/crash Solaris: WARNING: Can''t open objset for zroot/var/crash zpool status:

Hi all! I''ve decided to take the "big jump" and build a ZFS home filer (although it might also do "other work" like caching DNS, mail, usenet, bittorent and so forth). YAY! I wonder if anyone can shed some light on how long a pool scrub would take on a fairly decent rig. These are the specs as-ordered: Asus P5Q-EM mainboard Core2 Quad 2.83 GHZ 8GB DDR2/80 OS: 2 x