blob: 6c6b7f59d8dbc351af30436ec7a7c18b1f5334ba [file] [log] [blame]
Theodore Ts'o19c78dc1997-04-29 16:17:09 +00001Note: 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
4the '-b 8193' option first. The problem may lie only with
5the primary block group descriptor, and the backup block
6group 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
24Pass 4: Checking reference counts
25Pass 5: Checking group summary information
26Fix summary information? yes
27
28Block bitmap differences: -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 -20 -21. FIXED
29Free blocks count wrong for group 0 (78, counted=90). FIXED
30Free blocks count wrong (78, counted=90). FIXED
31Inode bitmap differences: -11. FIXED
32Free inodes count wrong for group #0 (21, counted=22). FIXED
33Directories count wrong for group #0 (2, counted=1). FIXED
34Free inodes count wrong (21, counted=22). FIXED
35
36test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
37test_filesys: 10/32 files (0.0% non-contiguous), 10/100 blocks
38Exit status is 1