From owner-freebsd-current@FreeBSD.ORG  Fri Jul  4 19:10:44 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 81372106568A
	for <current@freebsd.org>; Fri,  4 Jul 2008 19:10:44 +0000 (UTC)
	(envelope-from bakul@bitblocks.com)
Received: from mail.bitblocks.com (mail.bitblocks.com [64.142.15.60])
	by mx1.freebsd.org (Postfix) with ESMTP id 45C698FC14
	for <current@freebsd.org>; Fri,  4 Jul 2008 19:10:44 +0000 (UTC)
	(envelope-from bakul@bitblocks.com)
Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1])
	by mail.bitblocks.com (Postfix) with ESMTP id 87CFE5B4B;
	Fri,  4 Jul 2008 12:10:43 -0700 (PDT)
To: gnn@freebsd.org
In-reply-to: Your message of "Fri, 04 Jul 2008 12:58:07 EDT."
	<m2r6a9poww.wl%gnn@neville-neil.com> 
Date: Fri, 04 Jul 2008 12:10:43 -0700
From: Bakul Shah <bakul@bitblocks.com>
Message-Id: <20080704191043.87CFE5B4B@mail.bitblocks.com>
Cc: current@freebsd.org
Subject: Re: Has anyone else seen any form of in memory or on disk
	corruption? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jul 2008 19:10:44 -0000

On Fri, 04 Jul 2008 12:58:07 EDT gnn@freebsd.org  wrote:
> I have hundreds of these files to run this over, and a full check
> takes about 3 hours, but I usually see some form of corruption within
> the first 20 minutes.
> 	...
> 4) Corruption is seen only after a reboot, if the machines continue to
> run corruption is never seen again, until another reboot.

This sounds like a hardware problem....  May be heat related
or due to a marginal power supply?  Try using a beefier
supply on one of the systems or removing something to reduce
load.  Or increase the load by making disks do lots of
seeking while you are running unzip and running other things
at the same time.  To isolate heat related problems we used
to blow cold air (or hot air) on suspected components and see
if the problem goes away or gets worse.