> NAME STATE READ WRITE CKSUM > fatty DEGRADED 0 0 3.71K > raidz2 DEGRADED 0 0 3.71K > da0 ONLINE 0 0 0 > da1 ONLINE 0 0 0 > da2 ONLINE 0 0 0 > da3 ONLINE 0 0 300 > da4 ONLINE 0 0 0 > da5 ONLINE 0 0 0 > da6 ONLINE 0 0 253 > da7 ONLINE 0 0 0 > da8 ONLINE 0 0 0 > spare DEGRADED 0 0 0 > da9 OFFLINE 0 0 0 > da11 ONLINE 0 0 0 > da10 ONLINE 0 0 0 > spares > da11 INUSE currently in use > > errors: 801 data errors, use '-v' for a list > > > After I detach the spare da11 and bring da9 back online all the errors > go away.
Theory: Suppose da3 and da6 are either bad drives, have cabling issues, or are on a controller suffering corruption (different from the other drives). If you now were to replace da9 by da11, the resilver operation would be reading from these drives, thus triggering checksum issues. Once you bring da9 back in, it is either entirely up to date or very close to up to date, so the amount of I/O required to resilver it is very small and may not trigger problems. If this theory is correct, a scrub (zpool scrub fatty) should encounter checksum errors on da3 and da6. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
