Date: Wed, 14 Mar 2012 13:37:03 -0400 From: Mark Murawski <markm-lists@intellasoft.net> To: freebsd-fs@freebsd.org Subject: Re: ZFS file corruption problem Message-ID: <4F60D73F.2010201@intellasoft.net> In-Reply-To: <alpine.GSO.2.01.1203140858360.21564@freddy.simplesystems.org> References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net> <alpine.GSO.2.01.1203140858360.21564@freddy.simplesystems.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/14/12 10:03, Bob Friesenhahn wrote: > 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 Ah okay. And you assumed correctly that I had meant "become unavailable upon access". This is probably related to the bug I'm experiencing on my Promise SATA 300 TX4 controller (http://lists.freebsd.org/pipermail/freebsd-bugs/2012-March/047998.html)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F60D73F.2010201>