From owner-freebsd-net@FreeBSD.ORG Mon Apr 21 09:47:18 2008 Return-Path: Delivered-To: net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 04594106566C; Mon, 21 Apr 2008 09:47:18 +0000 (UTC) Date: Mon, 21 Apr 2008 09:47:18 +0000 From: Kris Kennaway To: "Arno J. Klaassen" Message-ID: <20080421094718.GY25623@hub.freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, net@freebsd.org Subject: Re: nfs-server silent data corruption X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2008 09:47:18 -0000 On Mon, Apr 21, 2008 at 01:02:33AM +0200, Arno J. Klaassen wrote: > I didn't stress-test this MB for a while, but last time I did was > with 7-PRELEASE/RC?/CANTremember-exactly-but-close-to-release > and all worked great > > I did add 2G ECC to the 2nd CPU since, though I doubt that interferes > with NFS. Uh, you're getting server-side data corruption, it could definitely be because of the memory you added. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe