Hello,
I am not subscribed to this list, so please CC me on replies.
I have just suffered from a filesystem crash on my laptop. It's an x86
running linux 2.6.22 from Ubutu latest gutsy.
This morning it booted and there were all kinds of strange core dumps.
fsck told me the root filesystem was clean,.
I then did a long test with smartctl which told me my disk was fine.
Then I forced fsck to check the filesystem (I was getting lots of files
not found), which then proceeded to fix plenty of errors, duplicate
missing or shared inodes, and many other errors I did not understand.
After pressing 'y' for about a hunderd times I was pretty convinced I
would not get my data back. Anyways after the 'fix' several parts of my
libc were removed and I cannot boot the system anymore (cannot get a
shell).
I had no idea my EXT3 filesystem could go wrong without notifying me
(fsck thought the filesystem was clean before I forced it). Is this
normal ?
If not, what can I do to figure out what went wrong ?
I am in the process of getting a live linux CD to look at the disk,
maybe there are some logs that can help.
Note that it's the first time I've lost a EXT3 (or EXT2) filesystem
without having experienced any system crash or power failure to explain
the filesystem problem. This machine booted and was turned off properly
for several weeks (at least).
Thanks for any help identifying the problem, I really hope this does not
happen again to me or anyone else.
--
Stéphane Epardaud
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
