[1024] in linux-scsi channel archive
Re: more scsi errors :(
daemon@ATHENA.MIT.EDU (Holger Schwenk)
Tue Nov 26 10:46:24 1996
Date: Tue, 26 Nov 1996 10:36:16 -0500
From: Holger Schwenk <schwenk@iro.umontreal.ca>
To: Gerard Roudier <groudier@club-internet.fr>
CC: Jon Lewis <jlewis@inorganic5.fdt.net>, "Theodore Y. Ts'o" <tytso@mit.edu>,
ncr53c810@colorado.edu,
Linux SCSI Mailing List <linux-scsi@vger.rutgers.edu>
Gerard Roudier wrote:
>
> Jon,
>
> The following patch should display in the log bad directory blocks at
> most every 30 seconds (avoid to stuff the log too much).
> If it is possible for you to give a try, we probably could have some
> information about the possible cause of ext2 dir blocks corruption.
> It is a hack. Check the source before try.
> It worked for me.
>
> .... patch itself deleted to save space ....
Hello,
with respect to the recent discussion about corrupted directory entries
on
SCSI drives I would like to add that I've had similar errors some weeks
ago.
I don't remember exactly the syntax, but there were very similar to
those
reported in this list some days ago.
However, I've got these errors on an EIDE system (Quantum Fireball 2.1
GB)
with no SCSI at all !!!
It happened to me when I unpacked a 128 Mb tar-archive (the Redhat RPMS
directory). I'vo also checked the filesystem immedeatly, but with no
errors.
Maybe this is a bug that happens under some very particular conditions,
for instance when creating directories containing a lot of big files ??
I should also add that I did the same operation later without any error
(but I'am not sure if it was the same kernel since I installed and
deinstalled
my systemn several times ;-).
This information is probably not very helpful, but at least it seems
that
the problems are not due to errors in the SCSI drivers.
Holger
