Date: Tue, 05 Feb 2008 12:00:29 -0700 From: Joe Peterson <joe@skyrush.com> To: Brooks Davis <brooks@freebsd.org> Cc: freebsd-fs@freebsd.org, Dag-Erling Sm??rgrav <des@des.no> Subject: Re: Forcing full file read in ZFS even when checksum error encountered Message-ID: <47A8B24D.9050904@skyrush.com> In-Reply-To: <20080205173102.GA85735@lor.one-eyed-alien.net> References: <47A73C8D.3000107@skyrush.com> <86prvby5o1.fsf@ds4.des.no> <47A864D9.4060504@skyrush.com> <864pcnxz8f.fsf@ds4.des.no> <47A88ADE.7050503@skyrush.com> <86abmfwc6h.fsf@ds4.des.no> <20080205173102.GA85735@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47A8B24D.9050904>