50 megs for the dumpe2fs output?!? How big is this file system? Can you send the dumpe2fs -h <device> output, then?
Actually, it's pretty clear what happened given that your bad block inode is completely trashed. It looks like random crap got written to the beginning of your file system. I'm surprised the superblock and block group descriptors looked valid enough that e2fsck didn't fail earlier. Were their any other e2fsck error messages that you didn't bother to include in your bug report, by any chance...? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861281 Title: FSCK on fs with claimed blocks yields Programming Error in process_bad_block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/861281/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
