Date: Tue, 5 Feb 2008 11:31:02 -0600 From: Brooks Davis <brooks@freebsd.org> To: Dag-Erling Sm??rgrav <des@des.no> Cc: freebsd-fs@freebsd.org Subject: Re: Forcing full file read in ZFS even when checksum error encountered Message-ID: <20080205173102.GA85735@lor.one-eyed-alien.net> In-Reply-To: <86abmfwc6h.fsf@ds4.des.no> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 05, 2008 at 06:22:30PM +0100, Dag-Erling Sm??rgrav wrote: > Joe Peterson <joe@skyrush.com> writes: > > Dag-Erling Sm??rgrav <des@des.no> writes: > > > There is now way to "read the bad data" since an unrecoverable > > > checksum error means that ZFS has no idea which of the multiple > > > version of the affected block is the right one. > > Nope, no mirror, no RAIDZ - just one partition. But as far as I know, = there > > were no read errors, just a checksum error. >=20 > A checksum error results from a read error. Check your drive's SMART > error log if it has one. It might not be detectable in a surface scan, > as the damaged sector will be automatically reassigned if it's written > to (which ZFS may very well have done) 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. -- Brooks --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHqJ1VXY6L6fI4GtQRAs8DAKCaaSkIJhcqe3WENQxt1qJsCjLdQwCfVNVq XsfLeRC8Mga3F+v3+vaaZrk= =29O6 -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080205173102.GA85735>