[1020] in linux-scsi channel archive
Re: more scsi errors :(
daemon@ATHENA.MIT.EDU (Jon Lewis)
Mon Nov 25 18:33:56 1996
Date: Mon, 25 Nov 1996 11:57:56 -0500 (EST)
From: Jon Lewis <jlewis@inorganic5.fdt.net>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
cc: Gerard Roudier <groudier@club-internet.fr>, ncr53c810@colorado.edu,
Linux SCSI Mailing List <linux-scsi@vger.rutgers.edu>
In-Reply-To: <9611251558.AA23805@dcl.MIT.EDU>
On Mon, 25 Nov 1996, Theodore Y. Ts'o wrote:
> At some point, I'll probably kill innd, umount sdd1, run e2fsck -fy
> on it, remount, and restart innd.
>
> Good idea. Better to do it sooner rather later. The presense of this
> error indicates at least some filesystem corruption, and it's better to
> catch this now rather than later.
Just did it...and it found nothing. This looks like it was just a
corrupted read from the disk that never really affected anything.
> What is still a mystery, of course, is *why* you have the filesystem
> corruption. It could be hardware related (and you seem to be exploring
> those). Besides a SCSI cabling problem, it could also be a wierd memory
> bug, or some kind of kernel bug (somewhat less likely given that I
I'll try improving the termination...active at both ends rather than
active/passive....but I'd hate to think it's RAM. We have 2 64mb simms in
the news server...and spares are hard to come by.
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/hr.
________Finger jlewis@inorganic5.fdt.net for PGP public key_______
