From owner-freebsd-fs@FreeBSD.ORG Tue Feb 5 19:06:37 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0C8716A41B; Tue, 5 Feb 2008 19:06:37 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 166F613C4E8; Tue, 5 Feb 2008 19:06:36 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.1/8.13.8) with ESMTP id m15J6S5N086766; Tue, 5 Feb 2008 13:06:28 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.1/8.13.8/Submit) id m15J6SQV086765; Tue, 5 Feb 2008 13:06:28 -0600 (CST) (envelope-from brooks) Date: Tue, 5 Feb 2008 13:06:28 -0600 From: Brooks Davis To: Joe Peterson Message-ID: <20080205190628.GA86728@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> <47A8B24D.9050904@skyrush.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: <47A8B24D.9050904@skyrush.com> User-Agent: Mutt/1.5.16 (2007-06-09) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Tue, 05 Feb 2008 13:06:28 -0600 (CST) Cc: freebsd-fs@freebsd.org, Dag-Erling Sm??rgrav , Brooks Davis Subject: Re: Forcing full file read in ZFS even when checksum error encountered X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 19:06:37 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > 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 fil= e was > written, and I think ZFS checks after writing. Strange. This is one rea= son > why I'm very curious which bits are bad. I'm not sure if they were consistent. We didn't really care since either t= he data one the disk was platter wasn't the data we put there or we couldn't r= ead reliably. We've not seen any checksum errors (in our somewhat limited experience) that weren't a symptom of a real, underlying problem. -- Brooks --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHqLOzXY6L6fI4GtQRAnNnAJoCZqqBdXS6DF3H4N4+QxXgF42UxACg3anr W9puMMUQ98Rq9hDD57Ay8u0= =o34K -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--