Oh, so I forgot to mention the main thing which caused e2fsck to report that various inode tables needed to be moved. The filesystem feature field was zero'ed out, and looking at the dumpe2fs output, it's clear the sparse_super feature should have been enabled. The backup superblocks should have that feature set; if so, running e2fsck telling it to pay attention to one of the backup superblocks should address the problem. Again, the really funny thing was how the superblock got corrupted in such a funny and specific way. It's almost as if it was corrupted by Murphy (as in Murphy's Law) himself. - Ted _______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
