Date: Fri, 04 Jul 2008 20:19:56 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: gnn@freebsd.org Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? Message-ID: <486E69CC.50205@FreeBSD.org> In-Reply-To: <m2r6a9poww.wl%gnn@neville-neil.com> References: <m2r6a9poww.wl%gnn@neville-neil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
gnn@freebsd.org wrote: > Hi, > > I've been working on the following brain teasing (breaking?) problem > for about a week now. What I'm seeing is that on large memory > machines, those with more than 4G of RAM, the ungzipping/untarring of > files fails due to gzip thinking the file is corrupt. The way to > reproduce this is: > > 1) Create a bunch of gzip/tar balls in the 1-20MB range. > 2) Reboot FreeBSD 7.0 release > 3) Run gzip -t over all the files. > > 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. > > Other important factors: > > 1) This is on very modern, 2P/4Core (8 cores total) hardware > 2) The disks are 1TB SATA set up in JBOD. > 3) The machines have 16G of RAM. > 4) Corruption is seen only after a reboot, if the machines continue to > run corruption is never seen again, until another reboot. > 5) The systems are all Xeon running amd64 > 6) The disk controller is an AMCC 9650, but we do see this very rarely > with the on board controlller. > 7) All boards are As a negative data point, I have a number of 2*4 core amd64 systems with 8GB of RAM and ATA disks that do not see data corruption (at boot or after it). Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?486E69CC.50205>