1) Update to something more recent that e2fsprogs 1.24 --- there have
been a lot of bugfixes since then, especially in the arena of dealing
with various "special" cases of corruption.
2) Assuming that you are using filesystems with 4k blocksizes, the
backup superblock is at 32768. More modern e2fsck's will correctly
fall back to the backup sb at 32768, but ancient versions (like the
one you're using) don't; that's one of the bugs that since been fixed. :-)
You could *try* using e2fsck -b 32768 with your current version of
e2fsck, and it *probably* will be able to fix things without doing any
more damage, but without knowing more about how your filesystem got
screwed up, using a more recent version of e2fsck would be the safer
course of action.
- Ted
-
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/