1 Note: if several inode or block bitmap blocks or part 2 of the inode table require relocation, you may wish to try 3 running e2fsck with the '-b 8193' option first. The problem 4 may lie only with the primary block group descriptors, and 5 the backup block group descriptors may be OK. 6 7 Inode table for group 0 is not in group. (block 40000) 8 WARNING: SEVERE DATA LOSS POSSIBLE. 9 Relocate? yes 10 11 ../e2fsck/e2fsck: A block group is missing an inode table while reading bad blocks inode 12 This doesn't bode well, but we'll try to go on... 13 Pass 1: Checking inodes, blocks, and sizes 14 Relocating group 0's inode table to 5... 15 Restarting e2fsck from the beginning... 16 Pass 1: Checking inodes, blocks, and sizes 17 Root inode is not a directory. Clear? yes 18 19 Pass 2: Checking directory structure 20 Pass 3: Checking directory connectivity 21 Root inode not allocated. Allocate? yes 22 23 /lost+found not found. Create? yes 24 25 Pass 4: Checking reference counts 26 Pass 5: Checking group summary information 27 Block bitmap differences: -(11--21) 28 Fix? yes 29 30 Free blocks count wrong for group #0 (77, counted=89). 31 Fix? yes 32 33 Free blocks count wrong (77, counted=89). 34 Fix? yes 35 36 Free inodes count wrong for group #0 (20, counted=21). 37 Fix? yes 38 39 Directories count wrong for group #0 (3, counted=2). 40 Fix? yes 41 42 Free inodes count wrong (20, counted=21). 43 Fix? yes 44 45 46 test_filesys: ***** FILE SYSTEM WAS MODIFIED ***** 47 test_filesys: 11/32 files (0.0% non-contiguous), 11/100 blocks 48 Exit status is 1 49
