ZFS file corruption problem

[Mark Murawski]

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)