> Mark Grant wrote: > I don't think ZFS does any timing out. > It's up to the drivers underneath to timeout and send > an error back to > ZFS - only they know what's reasonable for a given > disk type and bus > type.
I think that is the issue. By my reading, many (if not most) consumer drives don't put any internal time limit on how long they will continue trying to read a sector. In other words, if the drive encounters a read error, it may sit there forever trying to read the bad block without actually reporting an error. This is behavior is supposedly preferred (in consumer drives) because in a single drive setup, most users would rather have the drive try indefinitely to read a sector in the hopes of getting their data back rather than having less chance of recovery if the error recovery times out and the sector is marked as bad. Unless the controller, driver, or higher layers of the software stack time out a read request, the drive can hang the system. This issue has been discussed on the AVForums among other places. Richard -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
