whoops, corrupted my filesystem

Andreas Dilger adilger at clusterfs.com
Fri Mar 2 10:51:28 UTC 2007

On Mar 01, 2007  16:21 -0500, Andy Lindeman wrote:
> Doing a e2fsck /dev/hda2 tells me that the superblock is corrupt.   When I 
> do a mke2fs -n /dev/hda2, it tells me that other backups are stored on 
> 32768, 98304, 16840, 229376, 294912, 819200, 884736, 1605632, 265???? (cut 
> off), 4096000, 7962624, 11239424, 20480000, 23887872.
> When I try doing a e2fsck -b xxx /dev/hda2, on any of the superblocks <= 
> 4096000 I get the message that it's corrupted.  When I do >= 7962625, I get 
> "Invalid argument while trying to open /dev/hda2."
> By the way, there's some sort of weird Logical Volume thing going on with 
> this partition.  On an old (out of date unfortunately) backup, the mtab 
> file has it listed as /dev/mapper/VolGroup00-LogVol00.  Perhaps this 
> partition can't be addressed as /dev/hda2 and it should be addressed 
> differently??

Correct.  You should be running e2fsck /dev/mapper/VolGroup00-LogVol00
instead of /dev/hda2.  That's likely why your filesystem is "corrupted"...

Cheers, Andreas
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

More information about the Ext3-users mailing list