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