| Theodore Ts'o | a418d3a | 1997-04-26 14:00:26 +0000 | [diff] [blame] | 1 | These images contain various forms of corrupted filesystem which |
| 2 | e2fsck will correct. They are used as a regression test for e2fsck. |
| 3 | |
| 4 | The test_script program will automatically run e2fsck against the |
| 5 | filesystem images. It will run them two times, and display the exit |
| 6 | status for each run. The meaning of the exit status codes are as |
| 7 | follows: |
| 8 | |
| 9 | 0 No filesystem errors were detected |
| 10 | 1 Filesystem errors detected, but corrected |
| 11 | 2 System should be rebooted |
| 12 | 4 Filesystem errors left uncorrected |
| 13 | 8 Operational error (generally means internal error, |
| 14 | or filesystem error that the e2fsck was not |
| 15 | prepared to deal with) |
| 16 | 16 Usage or syntax error |
| 17 | |
| 18 | During the regression test, the first exit code should be 1, and the |
| 19 | second exit code should be 0. In other words, all (with one |
| 20 | exception) of the test filesystems in this directory have some sort of |
| 21 | filesystem corruption, which e2fsck should fix on the first pass. |
| 22 | After the first pass, e2fsck should leave a fully consistent |
| 23 | filesystem with no detectable errors found in the second pass. The |
| 24 | exception is the okgroup.img filesystem, which contains no errors, and |
| 25 | so both exit codes should be 0. |
| 26 | |
| 27 | NOTE: It appears that at least some versions of the original e2fsck do |
| 28 | not exit with an exit status code of 1 after correcting filesystem |
| 29 | errors. So if you modify the test_script to try running these |
| 30 | filesystems against the original e2fsck, you will have to inspect the |
| 31 | test_script.log file manually. |
| 32 | |
| 33 | -------------------------------------------------------------- |
| 34 | Here's a one-line descriptons of the various test images in this |
| 35 | directory: |
| 36 | |
| 37 | baddir.img Filesystem with a corrupted directory |
| 38 | badbblocks.img Filesystem with illegal blocks in the bad block inode. |
| 39 | badinode.img Filesystem with various different corrupted inode |
| 40 | entries. |
| 41 | badlkcnt.img Filesystem with deleted files with non-zero link count |
| 42 | badroot.img Filesystem with a file for a root directory |
| 43 | badtable.img Filesystem with blocks shared between the bitmaps and |
| 44 | inode table blocks and the bad block inode |
| 45 | bbfile.img Filesystem with files containing bad blocks |
| 46 | bitmaps.img Filesystem with corrupted inode and block bitmaps |
| 47 | dirlink.img Filesystem with a hard link to a directory |
| 48 | dup.img Filesystem with blocks claimed by two different files |
| 49 | dup2.img Filesystem with blocks claimed by three different files |
| 50 | dupfsblks.img Filesystem with blocks claimed by a file and |
| 51 | inode/block bitmaps and inode tables |
| 52 | dupsuper.img Filesystem with blocks claimed by a file and |
| 53 | the superblock / group descriptors |
| 54 | end-bitmap.img Filesystem with corruption at the end of the block |
| 55 | bitmap |
| 56 | expand.img Tests e2fsck's ability to expand lost+found if |
| 57 | necessary |
| 58 | lpf.img Filesystem with disconnected files and no /lost+found |
| 59 | directory |
| 60 | mke2fs2b.img Filesystem with corruption similar to that |
| 61 | created by mke2fs version 0.2b |
| 62 | noroot.img Filesystem with a deleted root directory |
| 63 | okgroup.img Filesystem that's exactly 8193 blocks long |
| 64 | (otherwise OK) |
| 65 | overfsblks.img Filesystem with overlapping inode and block bitmaps |
| Andreas Dilger | 67052a8 | 2001-08-04 00:51:18 -0600 | [diff] [blame] | 66 | symlinks.img Filesystem with bad symlink sizes |
| Theodore Ts'o | a418d3a | 1997-04-26 14:00:26 +0000 | [diff] [blame] | 67 | |
| 68 | |