Eaten filesystem and unhelpfull fsck

Eaten filesystem and unhelpfull fsck

[Pavel Machek]

Hi!

I managed to kill filesystem on my omnibook... Now I'm pretty sure
most of data should be undamaged [I did not do any long writes to it],
but mount refuses to mount it and e2fsck refuses that, too.

fsck /dev/hda4
fsck 1.24a (02-Sep-2001)
...
try running...:

	e2fsck -b 8193.

e2fsck -b 8193 /dev/hda4
....suggests me to run e2fsck -b 8193. Too bad. debugfs refuses to
mount it, too. How do I get my data back?
								Pavel
-- 
When do you have heart between your knees?

Re: Eaten filesystem and unhelpfull fsck

[Theodore Ts'o]

On Tue, Oct 15, 2002 at 10:05:11PM +0200, Pavel Machek wrote:
> Hi!
> 
> I managed to kill filesystem on my omnibook... Now I'm pretty sure
> most of data should be undamaged [I did not do any long writes to it],
> but mount refuses to mount it and e2fsck refuses that, too.
> 
> fsck /dev/hda4
> fsck 1.24a (02-Sep-2001)
> ...
> try running...:
> 
> 	e2fsck -b 8193.
> 
> e2fsck -b 8193 /dev/hda4
> ....suggests me to run e2fsck -b 8193. Too bad. debugfs refuses to
> mount it, too. How do I get my data back?

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