From owner-freebsd-stable@FreeBSD.ORG Mon Oct 20 16:57:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCC9F1065673 for ; Mon, 20 Oct 2008 16:57:18 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 9EEE68FC13 for ; Mon, 20 Oct 2008 16:57:18 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by QMTA06.emeryville.ca.mail.comcast.net with comcast id V22A1a00A0S2fkCA64xJC6; Mon, 20 Oct 2008 16:57:18 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA09.emeryville.ca.mail.comcast.net with comcast id V4xH1a00E2P6wsM8V4xHRV; Mon, 20 Oct 2008 16:57:18 +0000 X-Authority-Analysis: v=1.0 c=1 a=8pif782wAAAA:8 a=QycZ5dHgAAAA:8 a=Ls665AP9h_C1njxOEyIA:9 a=PmochnTLO1i0oo4NrAQZi1HcAv8A:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 4D787C9437; Mon, 20 Oct 2008 09:48:31 -0700 (PDT) Date: Mon, 20 Oct 2008 09:48:31 -0700 From: Jeremy Chadwick To: Chuck Swiger Message-ID: <20081020164831.GA8016@icarus.home.lan> References: <200810171530.45570.joao@matik.com.br> <200810200837.40451.joao@matik.com.br> <20081020132208.GA3847@icarus.home.lan> <98238FC8-0FC4-4410-829F-EF2EA16A57B8@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <98238FC8-0FC4-4410-829F-EF2EA16A57B8@mac.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org, JoaoBR Subject: Re: constant zfs data corruption X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2008 16:57:18 -0000 On Mon, Oct 20, 2008 at 09:44:50AM -0700, Chuck Swiger wrote: > Hi, all-- > > On Oct 20, 2008, at 6:22 AM, Jeremy Chadwick wrote: > [ ...JoaoBR wrote... ] >>> well, hardware seems to be ok and not older than 6 month, also >>> happens not >>> only on one machine ... smartctl do not report any hw failures on >>> disk >>> >>> regarding jumpering the drives to 150 you suspect a driver problem? >> >> It's not because of a driver problem. There are known SATA chipsets >> which do not properly work with SATA300 (particularly VIA and SiS >> chipsets); they claim to support it, but data is occasionally >> corrupted. >> Capping the drive to SATA150 fixes this problem. >> >> http://en.wikipedia.org/wiki/Serial_ATA#SATA_1.5_Gbit.2Fs_and_SATA_3_Gbit.2Fs > > Exactly so. Just as a general principle, if you've got sporadic data > corruption, turning I/O and system busses down a notch and retesting is a > useful starting point towards identifying whether the issue is > repeatable and whether it leans towards a hardware issue or software. > However, ZFS file checksumming supposedly is code that has been > carefully reviewed and tested so when it logs problems that is supposed > to be a fairly sure sign that the hardware isn't behaving right. Hm... I thought we determined earlier in this thread that the OP is not getting the benefits of ZFS checksums because he's not using raidz (only a single disk with a single pool)? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |