constant zfs data corruption
koitsu at FreeBSD.org
Mon Oct 20 09:57:18 PDT 2008
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
>>> 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
>> Capping the drive to SATA150 fixes this problem.
> 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 |
More information about the freebsd-stable