From owner-freebsd-stable@FreeBSD.ORG Mon Nov 13 15:25:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A41D16A4B3 for ; Mon, 13 Nov 2006 15:25:36 +0000 (UTC) (envelope-from jbozza@qlinksmedia.com) Received: from mail.thinkburst.com (mail.thinkburst.com [66.210.222.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B7A743D80 for ; Mon, 13 Nov 2006 15:20:56 +0000 (GMT) (envelope-from jbozza@qlinksmedia.com) Received: from mailgate.thinkburstmedia.com (gateway.thinkburstmedia.com [66.210.222.36]) by mail.thinkburst.com (Postfix) with ESMTP id DA2571CC27 for ; Mon, 13 Nov 2006 09:20:49 -0600 (CST) Received: from thinkburst.com (bacchus.thinkburst.com [10.1.1.25]) by mailgate.thinkburstmedia.com (Postfix) with ESMTP id CE28317046 for ; Mon, 13 Nov 2006 09:20:49 -0600 (CST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 13 Nov 2006 09:20:48 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Message-ID: In-Reply-To: <032501c705c5$6cefa790$9603a8c0@claylaptop> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 6-STABLE oddity Thread-Index: AccFxtFw8jWrKELmSEuEsxxVi/4n0wBbyy9A From: "Jaime Bozza" To: Subject: RE: 6-STABLE oddity 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, 13 Nov 2006 15:25:36 -0000 > Download, burn to CD and run http://www.memtest86.com/ >=20 > Usually problems of this sort are faulty ram. > I had a buddy getting odd errors on copying files that happenned at > random. > Turned out to be bad ram too. I recently had this same problem with a recent 6-STABLE and thought the same thing. Ran memtest for over 48 hours and never came up with any errors. I would cvsup source and run an md5 check to compare with another "known good" system and seemed to always have 1-2 files bad. It seemed to always be just 1 bit off. Tried swapping cables, cards (SCSI), etc. The system was running gmirror on two 18G SCSI drives using an Adaptec controller. If I disabled the 2nd drive, I didn't have a single problem after a ton of testing. Turned out that I hadn't formatted the 2nd drive using the Adaptec tools. The drives had been out of service for about 3 years. Once I went through a format/verify I wasn't able to duplicate the problem no matter what I tried. So, RAM is definitely the easiest thing to test but keep in mind that there are other areas that may also cause an issue. Jaime Bozza