To my mind it's a big limitation of ZFS that it relies on the driver timeouts. The driver has no knowledge of what kind of configuration the disks are in, and generally any kind of data loss is bad, so it's not unexpected to see that long timeouts are the norm as the driver does it's very best to avoid data loss.
ZFS however knows full well if a device is in a protected pool (whether raided or mirrored), and really has no reason to hang operations on that entire pool if one device is not responding. I've seen this with iSCSI drivers and I've seen plenty of reports of other people experiencing ZFS hangs, and that includes the admin tools which makes error reporting / monitoring kind of difficult too. When dealing with redundant devices ZFS needs to either have it's own timeouts, or a more intelligent way of handling this kind of scenario. This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
