The system is using the backup superblock -- which sounds* reasonable, under the circumstances, and should result in a half-decent recovery.
A couple of questions:
Was the superblock zero to begin with, or did it become zero during the FSCK?
In either case, I'm worried about the zero data having been written. This is obviously worth further investigation.
Did the system abort the FSCK after this error? or did you stop it?
did you try explicitly using one of the backup superblocks?
* a list of backup superblocks can be found by using -n on mkfs
* check the -b option on fsck.ext2 for more details on the backup superblock defaults.
2010/2/21 Albert Sellarès <email@example.com>
I'm trying to fix a 7.5Tb ext3 filesystem using e2fsck on a x86_64
machine with plenty of memory ram. The filesystem is corrupted, but I
can mount it.is
Before starting the filesystem check, I did a LVM snapshot to be able to
start it again from the same point in case of error.
After 12 hours checking the filesystem, I got this error message: