[lkml]   [2000]   [Nov]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ext2 filesystem corruptions back from dead? 2.4.0-test11
On Thu, 23 Nov 2000, Andre Hedrick wrote:

> Since there have been not kernel changes to the driver that effect the
> code since 2.4.0-test5 or test6 and it now randomly shows up after five or
> six revisions out from the change, and the changes were chipset only.
> Please make your point.

My point is simple: I'm trying to see if there is a pattern. I've had
filesystems corrupted with 2.2.18 + the backported IDE driver. Other
people have had filesystems corrupted with 2.4.0 + the same IDE driver.
If *all* people seeing f/s corruption have IDE disks and *none* of them
have SCSI, there might be something worth looking into. It might as well
be pure coincidence.

What's especially bothering me is the fact that I've seen the IDE driver
choke on DMA or something, and then continue on with life, while serving
*bad* *data* to the upper layers. Even if there were real problems with
the DMA transfers (which is not the case, 2.2.18pre without the IDE patch
runs flawlessly), a driver should never ever serve bad blocks to the f/s
layer. Locking up the machine completely, like some SCSI low-level drivers
do, is much better.

So I'm asking the same question, to all those who have seen unexplained
filesystem corruption with 2.4.0: are you using IDE drives? If the answer
is yes, can you check the logs and see if, at *any* point before the
corruption occurred, the IDE driver choked and disabled DMA for *any* of
your disks?

Even if 90% of the installed base is IDE and 10% is SCSI, in terms of how
heavily the hardware is being stressed the advantage of IDE over SCSI is
definitely not 9:1.

And Andre, don't take this personally. We're just trying to save our
precious data here, nothing more. :-) If something comes out of this
inquiry, it might just give you a lead.


It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:47    [W:0.058 / U:0.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site