On Fri, 8 Feb 2002, Pavel Machek wrote:
> Hi!
>
> > > > > 2.5.3 managed to damage my ext2 filesystem (few lost directories);
> > > > > beware.
> > >
> > > > I can confirm that there are filesystem corruption issues with 2.5.3;
> > > > after this message I rebooted and did a forced fsck which turned up
> > > > around a half dozen inodes where the block count in the inode itself was
> > > > too high.
> > >
> > > Exactly the same thing here, and I bet it _is_ 2.5.3 and not a relict from
> > > a 2.5.3-pre patch because I switched directly from 2.4.17 to 2.5.3
> > > without ever using any pre patch at this machine.
> >
> > Very interesting. Which filesystems are mounted (other than ext2) and
> > are you been able to reproduce it on 2.5.3-pre6?
>
> Mounted filesystems:
>
> /dev/hda2 on / type ext2 (rw)
> none on /proc type proc (rw)
> ...
> none on /proc type proc (rw)
> /dev/hda3 on /suse type ext2 (rw)
> none on /proc type proc (rw)
> none on /proc/bus/usb type usbdevfs (rw)
> /dev/cfs0 on /overlay type coda (rw)
>
> (I wander what is responsible for mounting /proc hundred times?)
>
> But... you should know that I'm strongly suspecting ide subsystem:
>
> Feb 8 12:08:02 amd kernel: hda: status timeout: status=0xd0 { Busy }
> Feb 8 12:08:02 amd kernel: hda: drive not ready for command
> Feb 8 12:08:02 amd kernel: ide0: reset: success
> Feb 8 12:09:26 amd kernel: hda: status timeout: status=0xd0 { Busy }
> Feb 8 12:09:26 amd kernel: hda: drive not ready for command
> Feb 8 12:09:26 amd kernel: ide0: reset: success
> Feb 8 12:12:27 amd kernel: hda: status timeout: status=0xd0 { Busy }
> Feb 8 12:12:27 amd kernel: hda: drive not ready for command
> Feb 8 12:12:27 amd kernel: ide0: reset: success
>
> I'm trying to test it with md5sum, but so far it behaves ok. [I wonder
> what directory I'll loose this time ... :-(]
> Pavel
>
> --
> (about SSSCA) "I don't say this lightly. However, I really think that the U.S.
> no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Yep I warned about multmode pio.
I think I finally have a fix which does not use a copy of the request.
Andre Hedrick
Linux Disk Certification Project Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:00:23 EST