Forcing full file read in ZFS even when checksum error encountered

Brooks Davis brooks at freebsd.org
Tue Feb 5 19:06:37 UTC 2008


On Tue, Feb 05, 2008 at 12:00:29PM -0700, Joe Peterson wrote:
> Brooks Davis wrote:
> > We've also experienced several situations were zfs was detecting
> > corruption caused by bad cabling or bad controller firmware so SMART had
> > nothing to report.
> 
> Were the errors sporadic/intermittent?  I'd think that if it was cabling, the
> checksum error could happen some times and not others.  Mine seems to be
> predictable and always there...  Also, no error was reported when the file was
> written, and I think ZFS checks after writing.  Strange.  This is one reason
> why I'm very curious which bits are bad.

I'm not sure if they were consistent.  We didn't really care since either the
data one the disk was platter wasn't the data we put there or we couldn't read
reliably.  We've not seen any checksum errors (in our somewhat limited
experience) that weren't a symptom of a real, underlying problem.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20080205/c98abbb1/attachment.pgp


More information about the freebsd-fs mailing list