From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 00:38:55 2008 Return-Path: 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 DD755106566C; Tue, 8 Jul 2008 00:38:55 +0000 (UTC) (envelope-from lsc@prgmr.com) Received: from luke.xen.prgmr.com (luke.xen.prgmr.com [38.99.2.47]) by mx1.freebsd.org (Postfix) with ESMTP id 9BA778FC14; Tue, 8 Jul 2008 00:38:55 +0000 (UTC) (envelope-from lsc@prgmr.com) Received: by luke.xen.prgmr.com (Postfix, from userid 500) id 483B71041CC; Mon, 7 Jul 2008 20:19:50 -0400 (EDT) Sender: lsc@luke.xen.prgmr.com To: gnn@freebsd.org References: From: Luke S Crawford Date: 07 Jul 2008 20:19:50 -0400 In-Reply-To: Message-ID: Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 00:38:56 -0000 gnn@freebsd.org writes: > 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. I've seen similar problems happen on a groups of new boxes when the ram was slightly out of spec for the motherboard. memtest revealed the problem, returning the lot of ram for a different model fixed the problem. > 4) Corruption is seen only after a reboot, if the machines continue to > run corruption is never seen again, until another reboot. This would indicate that I am wrong. Personally, I'd still run memtest86 for 48 hours or so, just to be sure. does smartctl report weirdness?