ZFS file corruption problem

[George Kontostanos]

On Wed, Mar 14, 2012 at 7:37 PM, Mark Murawski
<markm-lists at intellasoft.net> wrote:
> 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)
>
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"

Yes, as a matter of fact:

http://www.aisecure.net/2011/07/07/promise-pdc40718-sata300-junk/

-- 
George Kontostanos
Aicom telecoms ltd
http://www.aisecure.net