Invalid superblock after e2fsck
sandeen at redhat.com
Tue Feb 23 15:16:07 UTC 2010
Albert Sellarès wrote:
> I have the original filesystem (on a logical volume) "intact" because I've
> always worked on snapshots.
> The filesystem has less than 2^31 blocks. This system has been correctly
> running for four years and corruption become because of a hardware problem
> with a SAN device.
> The output of dumpe2fs -h /dev/storage/cabina is:
> dumpe2fs 1.41.9 (22-Aug-2009)
> Block count: 2077085696
> Block size: 4096
Yep, right you are, just figured it was worth a check.
Since you can safely operate on a snapshot, -maybe- it would be worth
testing with an e2fsprogs which is newer than that which ships with rhel4...
this wouldn't be a RHEL-supported option, but if there is something which
has been fixed upstream it would help identify the problem if
we knew which release fixed it.
More information about the Ext3-users