Package: e2fsprogs
Version: 1.41.3-1
During a routine filesystem check at boot, e2fsck discovered the following:
# /dev/vg2/backuppc has gone 264 days without being checked,
# check forced.
# /dev/vg2/backuppc: Group 15625's block bitmap at 512001023 conflicts
# with some other fs block.
# /dev/vg2/backuppc: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
# (i.e., without -a or -p options)
Running fsck manually produced:
# e2fsck 1.41.3 (12-Oct-2008)
# e2fsck: Group descriptors look bad... trying backup blocks...
# e2fsck: Bad magic number in super-block while trying to open
# /dev/vg2/backuppc
#
# 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 8193 <device>
I tried various of the backup superblocks as reported by mke2fs -n,
but e2fsck always said:
# e2fsck 1.41.3 (12-Oct-2008)
# e2fsck: Bad magic number in super-block while trying to open
# /dev/vg2/backuppc
leaving me unable to repair the filesystem.
The e2fsprogs changelog for 1.41.0 mentions some changes relating to
corrupted block group descriptors, so I tried the version from etch
(1.39+1.40-WIP-2006.11.14+dfsg-2etch1). It relocated some tables
(sorry, no transcript) and a subsequent e2fsck found no further issues.
So some change since etch caused e2fsck to no longer be able to fix
this problem.
--Benjamin Gilbert
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
