While attempting to expand a 1.64T ext4 volume to 2.18T the F9 kernel deadlocked. (I have photo of screen/oops if anybody's interested.) Now after recovery, the filesystem won't mount EXT4-fs: ext4_check_descriptors: Block bitmap for group 13413 not in group (block 0)!<3>EXT4-fs: group descriptors corrupted! and fsck won't run: fsck.ext4: Group descriptors look bad... trying backup blocks... inst: recovering journal fsck.ext4: unable to set superblock flags on inst I peeked at all backup superblocks, but they all appear the same--the larger/newer 2.18T geometry. :-( What is the best way to recover? I know exactly how the original filesystem was created. Is there a way to just replay the old superblocks and trick it into thinking it never resized? ../C dumpe2fs 1.41.0 (10-Jul-2008) Filesystem volume name: inst Last mounted on: <not available> Filesystem UUID: ddabbf0c-bf3f-495a-9777-e832cc14e9df Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent sparse_super large_file Filesystem flags: signed_directory_hash test_filesystem Default mount options: journal_data_writeback Filesystem state: clean Errors behavior: Remount read-only Filesystem OS type: Linux Inode count: 9080832 Block count: 581173248 Reserved block count: 5808792 Free blocks: 6282771 Free inodes: 4331111 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 885 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 512 Inode blocks per group: 16 RAID stride: 32 RAID stripe width: 64 Filesystem created: Sun Jul 27 21:02:11 2008 Last mount time: Wed Aug 13 18:28:35 2008 Last write time: Sat Oct 18 12:39:13 2008 Mount count: 2 Maximum mount count: -1 Last checked: Sun Jul 27 21:02:11 2008 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: tea Directory Hash Seed: c6e2cfa3-0545-46a4-8240-ccb987191b88 Journal backup: inode blocks Journal size: 256M
On Sat, Oct 18, 2008 at 12:55:56PM -0700, Curtis Doty wrote:> While attempting to expand a 1.64T ext4 volume to 2.18T the F9 kernel > deadlocked. (I have photo of screen/oops if anybody's interested.)Yes, that would be useful, thanks.> Now after recovery, the filesystem won't mount > > EXT4-fs: ext4_check_descriptors: Block bitmap for group 13413 not in > group (block 0)!<3>EXT4-fs: group descriptors corrupted! > > and fsck won't run: > > fsck.ext4: Group descriptors look bad... trying backup blocks... > inst: recovering journal > fsck.ext4: unable to set superblock flags on instHmm... This sounds like the needs recovery flag was set on the backup superblock, which should never happen. Before we try something more extreme, see if this helps you: e2fsck -b 32768 -B 4096 /dev/where-inst-is-located That forces the use of the backup superblock right away, and might help you get past the initial error. - Ted