On 09/18/10 04:28 AM, Tom Bird wrote:
Bob Friesenhahn wrote:
On Fri, 17 Sep 2010, Tom Bird wrote:
Morning,
c7t5000CCA221F4EC54d0 is a 2T disk, how can it resilver 5.63T of it?
This is actually an old capture of the status output, it got to
nearly 10T before deciding that there was an error and not
completing, reseat disk and it's doing it all again.
You have twice as many big slow drives in a raidz2 that any sane
person would recommend. It looks like you either have drives which
are too weak to sustain resilvering a failed disk, or a chassis which
is not strong enough.
The drives and the chassis are fine, what I am questioning is how can
it be "resilvering" more data to a device than the capacity of the
device?
Is the pool in use? If so, data will be changing while the resliver is
running. With such a ridiculously wide vdev and large drives, the
resliver will take a very very long time it complete. if the pool is
sufficiently busy, it may never complete.
Your only option seems to be to also replace c7t5000CCA221DE2225d0
and hope for the best. Expect the replacement to take a very long time.
It is wise to restart the pool from scratch with multiple vdevs
comprised of fewer devices.
This stuff should just work, if it only rewrote the <2T that was meant
to be on the drive the rebuild would take a day or so.
Bob's comments about the pool design are correct, you have a disaster
waiting to happen.
--
Ian.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
