From owner-freebsd-bugs@FreeBSD.ORG  Tue Sep 28 09:43:07 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 30F7F16A4CE; Tue, 28 Sep 2004 09:43:07 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 20CFA43D58; Tue, 28 Sep 2004 09:43:07 +0000 (GMT)
	(envelope-from sos@FreeBSD.org)
Received: from freefall.freebsd.org (sos@localhost [127.0.0.1])
	i8S9h75j013270;	Tue, 28 Sep 2004 09:43:07 GMT
	(envelope-from sos@freefall.freebsd.org)
Received: (from sos@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8S9h6QF013266;
	Tue, 28 Sep 2004 09:43:06 GMT
	(envelope-from sos)
Date: Tue, 28 Sep 2004 09:43:06 GMT
From: Søren Schmidt <sos@FreeBSD.org>
Message-Id: <200409280943.i8S9h6QF013266@freefall.freebsd.org>
To: jacke@bofh.pl, sos@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/72062: Inconsistency of large files on RAID1 with HPT372.
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2004 09:43:07 -0000

Synopsis: Inconsistency of large files on RAID1 with HPT372.

State-Changed-From-To: open->closed
State-Changed-By: sos
State-Changed-When: Tue Sep 28 09:34:26 GMT 2004
State-Changed-Why: 

You definitly have HW problems, I've hooked up a '372 here and have
banged on it to no avail, it just works (se below).
At any rate since UDMA uses CRC on the transfer from disk to memory
you should be getting ICRC errors if there was corruption underways.
Now since you dont state that, I'm 99.9% certain that your motherboard
has severe busmaster problems. We have seen corruption issues like this
before on badly designed boards, but it could also be a one of. 
Please try other controllers in there and check if that eventually works
(experience shows that this makes a significant difference), you might be
lucky to find a combo that works, but my advise would be to get the 
board RMA'd or maybe try a BIOS update.

pizzabox> md5 *
MD5 (xx_CD1.avi) = 13bd1c548bd540b82e5152bc29912094
MD5 (xx_CD2.avi) = a7942d255f0500b7d1233695c56375b6
MD5 (xx_CD3.avi) = 1d5517fa2ea2d2147bf74b7e95ca8d75
MD5 (xx_CD4.avi) = ee0d00b76f584fa16367841174d74454
pizzabox> md5 *
MD5 (xx_CD1.avi) = 13bd1c548bd540b82e5152bc29912094
MD5 (xx_CD2.avi) = a7942d255f0500b7d1233695c56375b6
MD5 (xx_CD3.avi) = 1d5517fa2ea2d2147bf74b7e95ca8d75
MD5 (xx_CD4.avi) = ee0d00b76f584fa16367841174d74454
pizzabox> md5 *
MD5 (xx_CD1.avi) = 13bd1c548bd540b82e5152bc29912094
MD5 (xx_CD2.avi) = a7942d255f0500b7d1233695c56375b6
MD5 (xx_CD3.avi) = 1d5517fa2ea2d2147bf74b7e95ca8d75
MD5 (xx_CD4.avi) = ee0d00b76f584fa16367841174d74454
pizzabox> md5 *
MD5 (xx_CD1.avi) = 13bd1c548bd540b82e5152bc29912094
MD5 (xx_CD2.avi) = a7942d255f0500b7d1233695c56375b6
MD5 (xx_CD3.avi) = 1d5517fa2ea2d2147bf74b7e95ca8d75
MD5 (xx_CD4.avi) = ee0d00b76f584fa16367841174d74454


http://www.freebsd.org/cgi/query-pr.cgi?pr=72062