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