Mailinglist Archive: opensuse (3139 mails)

["Greg Wallace" <gregwallace@xxxxxxxxxxx>]

I am using the EXT3 file system.  Today, I powered on the machine and went
into the other room for a few minutes while it booted up.  When I came back,
it turned out that it had come time for an fsck on the disk and the disk was
so corrupted that it couldn't be mounted in rw mode.  I had to log in to
non-grapchicakl mode and run e2fsck on the disk.  It was so corrupted that,
after repairing a few sectors (or whatever those low level repair operations
apply to) it said there was so much corruption that it had to repair an
entire inode.  It eventually repaired everything and I was able to boot back
up.  Normally, when there is a problem of this nature, the errors are fixed
on the fly and the boot process just continues with a normal log in.  I
thought EXT3 was able to do that via its journal in all cases.  I used to
get hit with this problem quite often under EXT2, but never under EXT3.  Is
this unusual that EXT3 couldn't recover the disk without me having to run
e2fsck?  Also, I looked at lost+found and didn't see anything in there so
can I assume that everything was recovered, or would I have lost data in
this instance?

Thanks,
Greg Wallace