From: linux-ext4-owner@xxxxxxxxxxxxxxx [mailto:linux-ext4- > > On May 09, 2009 14:36 -0400, Don Bowman wrote: > > To follow my own email, the results of the 'findsuper' program are: > > > > starting at 0, with 512 byte increments > > byte_offset byte_start byte_end fs_blocks blksz grp > last_mount_time sb_uuid label > > 1024 0 6001228775424 1465143744 4096 0 Wed ... > > > > Can this help me somehow? > > These are all showing available backup superblocks and group > descriptors. > Pick one of the "grp" numbers and use that as the argument for "-b" per > my previous email: "e2fsck -f -b $((729 * 32768)) -B 4096 /dev/XXX". > A backup first is still a good idea, however. > > Note that this appears to be a bug that has been hit by several Ubuntu > users. I would suggest to upgrade to the latest vanilla kernel (at > least 2.6.29.stable, search the archives for details), which has fixed > it for many users. So i upgraded to 2.26.29 generic. I than ran e2fsck as above. It ran for ~4 days, and then produced this after processing ~100% of the inodes: Error allocating 512 contiguous block(s) in block group 44709 for inode table: Could not allocate block in ext2 filesystem Relocating group 44710's block bitmap to 1465057282... Relocating group 44712's block bitmap to 1465122817... Relocating group 44712's inode table to 1465132694... Resize inode (re)creation failed: A block group is missing an inode table.Abort? yes e2fsck: aborted so am i stuck? -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
