Date: Mon, 20 Oct 2008 09:44:50 -0700 From: Chuck Swiger <cswiger@mac.com> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-stable@freebsd.org, JoaoBR <joao@matik.com.br> Subject: Re: constant zfs data corruption Message-ID: <98238FC8-0FC4-4410-829F-EF2EA16A57B8@mac.com> In-Reply-To: <20081020132208.GA3847@icarus.home.lan> References: <200810171530.45570.joao@matik.com.br> <E3C2EAB9-12ED-4D3E-B07A-E2FF5892D26A@mac.com> <200810200837.40451.joao@matik.com.br> <20081020132208.GA3847@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > There are also known problems with Silicon Image chipsets (on Linux, > Windows, and FreeBSD). Particularly with the 3112/4/x variants. My understanding is that the later 312x/313x chipsets are "better" in the sense that an improvement to something bad is a relative status not denoting "approval". :-) > Because you didn't provide your smartctl output, I can't really tell > if > the drives are in "good shape" or not. :-) > > Also, do you not think it's a little odd that the only data corruption > occurring for you are related to RRDtool? RRD tends to involve lots of small writes so it's files are going to be changed often compared to other things that might be running; a busy webserver or mailserver would involve more I/O to logfiles and queue/mailspool, or so I would expect, but who knows what the machine in question is being used for? Regards, -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98238FC8-0FC4-4410-829F-EF2EA16A57B8>