I just tried this using fsck.ext3 from e2fsprogs version 1.41.14-1ubuntu3 as
currently available in oneiric, and the output is:
$ fsck.ext3 -fpC0 dummy
dummy: Superblock has an invalid journal (inode 8).
CLEARED.
*** ext3 journal has been deleted - filesystem is now ext2 only ***
dummy: Corruption found in superblock. (frags_per_group = 0).
dummy:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 32768 <device>
No segfault or crash any more. Can you confirm this?
** Changed in: e2fsprogs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722398
Title:
fsck.ext3 segfault on corrupt filesystem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/722398/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
