Date: Thu, 17 Dec 1998 08:32:58 +0000 From: Neil Conway <nconway.list@ukaea.org.uk> To: Doug Ledford <dledford@redhat.com> Cc: Stephane Bortzmeyer <stephane@sources.org>, aic7xxx@FreeBSD.ORG Subject: Re: File corruption: how to find the guilty? Message-ID: <98Dec17.083132gmt.66308@gateway.ukaea.org.uk> References: <199812161347.OAA02367@ludwigV.sources.org> <3677BCBE.46D77E3B@redhat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Ledford wrote: > > Stephane Bortzmeyer wrote: > > > > I have a Linux box which shows random corruption of files. Example: all Perl > > scripts suddenly die with "segmentation fault". Reinstalling the same Perl > > package cures it. Two days ago, /etc/resolv.conf became corrupted : strange > > characters were in it. > > > > I wonder what to do? Change the disk? The SCSI controller? The kernel? > > > > I run Linux 2.0.35 (Debian distribution 2.0), patched for the Adaptec driver > > 5.1.2. Here is the configuration: > > It's memory corruption. I've seen this float through this list or that about > 30 different times in the past. Not once has it ever been a kernel or driver > issue. In *every* case it has been either RAM, cache, or CPU. Check the CPU > fan, check the cache (if it isn't part of the CPU) and check your RAM. Well perhaps with a stable kernel this is the most likely culprit. However, it's dangerous to make blanket assertions - they come back to haunt you. Alan Cox was telling me last month about how 2.1.129 was causing him random memory corruption leading to disk corruption, and this turned out to be a kernel bug (nfs-related I think). Neil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98Dec17.083132gmt.66308>