On Tue, Oct 30, 2007 at 03:59:24PM +0200, Heikki Orsila wrote:
> 3. fsck -p on boot failed
>
> (it is very probable not many files were corrupted at this stage)
Maybe...
>
> 4. I ran fsck.ext3 -y
>
> => that corrupted lots and lots of files. This went
> into a loop, the fsck.ext3 restarted checking over and over again.
It's possible that e2fsck corrupted the files, but they also could
have been corrupted earlier by the earlier I/O errors. There are some
relatively rare filesystem corruptions which e2fsck doesn't handle as
gracefully as it should, though, I will admit. I would need to see
the e2fsck transcript to be sure.
Were there any messages about needing to relocate inode tables by any
chance?
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
