On September 26, 2002 12:51, Horst von Brand wrote:
> > The interesting fsck errors this time were:
> > 245782 was part of the orphaned inode list FIXED
> > 245792 was part of the orphaned inode list FIXED
> > 245797...
> > 245782,245792 don't exist according to ncheck.
> Old(ish) WD disk, perhaps PIIX IDE? At home I get filesystem corruption if
> DMA is enabled...
No, 40GB Maxtor, VT133A chipset. This box has experienced -zero- filesystem
corruption since it was purchased, up until I tried the directory index
patch. And even then, it only shows up with the dir_index flag set.
OTOH, much of this corruption could be because journal replay doesn't seem to
be happening after a filesystem is remounted read-only due to errors. That
would certainly leave the filesystem in an inconsistant state.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
-----END PGP SIGNATURE-----
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/