Date: Wed, 14 Mar 2012 09:03:19 -0500 (CDT) From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us> To: Mark Murawski <markm-lists@intellasoft.net> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS file corruption problem Message-ID: <alpine.GSO.2.01.1203140858360.21564@freddy.simplesystems.org> In-Reply-To: <4F60266D.1090302@intellasoft.net> References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 14 Mar 2012, Mark Murawski wrote: > > Why would the whole pool now become available upon access to a bad file? A disk drive (or HBA) may be hanging (e.g. endless retries) when the bad file is accessed. This is a common problem with consumer disks or HBAs which believe they are the top level authority when it comes to data integrity. Zfs itself does not include any timers to decide to stop waiting. Zfs depends on the lower-level OS & drivers to decide to stop waiting on a stalled device. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.01.1203140858360.21564>