[Bug 722398] Re: fsck.ext3 segfault on corrupt filesystem

[Andrew McCarthy]

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
Foundations Bugs, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/722398

Title:
  fsck.ext3 segfault on corrupt filesystem

Status in “e2fsprogs” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: e2fsprogs

  In some cases fsck.ext3 segfaults on corrupted file systems. The
  attached file contains nine sectors that can reproduce the crash. This
  is the command I used to reproduce the crash:

  rm dummy ; for F in [1-9]* ; do dd if=$F of=dummy conv=notrunc seek=$F
  ; done 2>/dev/null ; fsck.ext3 -fpC0 dummy

  ProblemType: Bug
  Architecture: i386
  Date: Mon Feb 21 01:41:39 2011
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
  Package: e2fsprogs 1.41.9-1ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-22.70-generic
  SourcePackage: e2fsprogs
  Uname: Linux 2.6.31-22-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/722398/+subscriptions