Date: 21 Apr 2008 20:30:48 +0200 From: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: Kris Kennaway <kris@freebsd.org>, stable@freebsd.org Subject: Re: nfs-server silent data corruption Message-ID: <wp4p9vawmf.fsf@heho.snv.jussieu.fr> In-Reply-To: <20080421154333.GA96237@eos.sc1.parodius.com> References: <wpmyno2kqe.fsf@heho.snv.jussieu.fr> <20080421094718.GY25623@hub.freebsd.org> <wp63ubp8e0.fsf@heho.snv.jussieu.fr> <20080421154333.GA96237@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
yet another quick partial answer : Jeremy Chadwick <koitsu@freebsd.org> writes: > On Mon, Apr 21, 2008 at 04:52:55PM +0200, Arno J. Klaassen wrote: > > Kris Kennaway <kris@FreeBSD.ORG> writes: > > > Uh, you're getting server-side data corruption, it could definitely be > > > because of the memory you added. > > > > yop, though I'm still not convinced the memory is bad (the very same > > Kingston ECC as the 2*1G in use for about half a year already) : > > Can you download and run memtest86 on this system, with the added 2G ECC > insalled? memtest86 doesn't guarantee showing signs of memory problems, > but in most cases it'll start spewing errors almost immediately. It's running for 15 minutes now without any warning; I'll let it run while cooking a meal [ with 2*1G mem for each CPU to be clear ]. NB, (CC to kris@ for this) why is memtest86 port marked as i386-only? It only seems to install floppy.bin and memtest.iso, but alas (maybe I should leave one box dedicated to freebsd-i386 for things like this ;) ) Best, Arno
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wp4p9vawmf.fsf>