On 17.09.09 13:29, Chris Murray wrote:
I can flesh this out with detail if needed, but a brief chain of events is:
It would be nice to know what OS version/build/patchlevel are you running.
1. RAIDZ1 zpool with drives A, B, C & D (I don't have access to see original drive names) 2. New disk E. Replaced A with E. 3. Part way through resilver, drive D was 'removed' 4. 700+ persistent errors detected, and lots of checksum errors on all drives. Surprised by this - I thought the absence of one drive could be tolerated? 5. Exported, rebooted, imported. Drive D present now. Good. :-) 6. Drive D disappeared again. Bad. :-( 7. This time, only one persistent error. Does this mean that there aren't errors in the other 700+ files that it reported the first time, or have I lost my chance to note these down, and they are indeed still corrupt?
It depends on where that one persistent error is. If it is in some filsystem metadata, ZFS may no longer be able to reach to other error blocks as a result...
So it's impossible to tell without a bit more details. victor
I've re-ran step 5 again, so it is now on the third attempted resilver. Hopefully drive D won't remove itself again, and I'll actually have 30+ hours of stability while the new drive resilvers ...
Chris
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
