Has the issue with "disappearing" single-LUN zpools causing corruption
been fixed?
I'd have to look up the bug, but I got bitten by this last year about
this time:
Config:
single LUN export from array to host, attached via FC.
Scenario:
(1) array is turned off while host is alive, but while zpool is idle (no
write/reads occuring).
(2) host is shutdown
(3) array is turned on
(4) host is turned on
(5) host reports zpool is corrupted, refuses to import it, kernel
panics, and goes into a reset loop.
(6) cannot import zpool on another system, zpool completely hosed.
Now, IIRC, the perpetual panic and reboot thing got fixed, but not the
underlying cause, which was that zfs expected to be able to periodically
write/read metadata from a zpool, and the disappearance of the single
underlying LUN caused the zpool to be declared corrupted and dead, even
though no data was actually bad. The bad part of this is that the
scenario is entirely likely to happen if a bad HBA or Switch causes the
disappearance of the LUN, not the array itself going bad.
I _still_ don't do single-LUN non-redundant zpools because of this. Did
it get fixed, or is this still an issue?
--
Erik Trimble
Java System Support
Mailstop: usca22-123
Phone: x17195
Santa Clara, CA
Timezone: US/Pacific (GMT-0800)
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
