>>>>> "tn" == Thomas Nau <[EMAIL PROTECTED]> writes:
tn> Nevertheless during the first hour of operation after onlining
tn> we recognized numerous checksum errors on the formerly
tn> offlined device. We decided to scrub the pool and after
tn> several hours we got about 3500 error in 600GB of data.
Did you use 'zpool offline' when you took them down, or did you
offline them some other way, like by breaking the network connection,
stopping the iSCSI target daemon, or 'iscsiadm remove
discovery-address ..' on the initiator?
This is my experience, too (but with old b71). I'm also using iSCSI.
It might be a variant of this:
http://bugs.opensolaris.org/view_bug.do?bug_id=6675685
checksum errors after 'zfs offline ; reboot'
Aside from the fact the checksum-errored blocks are silently not
redundant, it's also interesting because I think, in general, there
are a variety of things which can cause checksum errors besides
disk/cable/controller problems. I wonder if they're useful for
diagnosing disk problems only in very gently-used setups, or not at
all?
Another iSCSI problem: for me, the targets I've 'zpool offline'd will
automatically ONLINE themselves when iSCSI rediscovers them. but only
sometimes. I haven't figured out how to predict when they will and
when they won't.
pgpo9BOlPemM3.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
