• Home
  • History
  • Annotate
  • only in /external/e2fsprogs/tests/
NameDateSize

..14-Feb-20134 KiB

d_loaddump/14-Feb-20134 KiB

defaults/14-Feb-20134 KiB

e_brel_bma/14-Feb-20134 KiB

e_icount_normal/14-Feb-20134 KiB

e_icount_opt/14-Feb-20134 KiB

e_irel_ima/14-Feb-20134 KiB

f_16384_block/14-Feb-20134 KiB

f_8192_block/14-Feb-20134 KiB

f_bad_disconnected_inode/14-Feb-20134 KiB

f_bad_local_jnl/14-Feb-20134 KiB

f_badbblocks/14-Feb-20134 KiB

f_baddir/14-Feb-20134 KiB

f_baddir2/14-Feb-20134 KiB

f_baddotdir/14-Feb-20134 KiB

f_badinode/14-Feb-20134 KiB

f_badjour_indblks/14-Feb-20134 KiB

f_badjourblks/14-Feb-20134 KiB

f_badorphan/14-Feb-20134 KiB

f_badprimary/14-Feb-20134 KiB

f_badroot/14-Feb-20134 KiB

f_badsymlinks/14-Feb-20134 KiB

f_badtable/14-Feb-20134 KiB

f_bbfile/14-Feb-20134 KiB

f_bbinode/14-Feb-20134 KiB

f_big_sparse/14-Feb-20134 KiB

f_bitmaps/14-Feb-20134 KiB

f_clear_xattr/14-Feb-20134 KiB

f_crashdisk/14-Feb-20134 KiB

f_dir_bad_mode/14-Feb-20134 KiB

f_dirlink/14-Feb-20134 KiB

f_dup/14-Feb-20134 KiB

f_dup2/14-Feb-20134 KiB

f_dup3/14-Feb-20134 KiB

f_dup4/14-Feb-20134 KiB

f_dup_de/14-Feb-20134 KiB

f_dup_de2/14-Feb-20134 KiB

f_dup_resize/14-Feb-20134 KiB

f_dupdot/14-Feb-20134 KiB

f_dupfsblks/14-Feb-20134 KiB

f_dupsuper/14-Feb-20134 KiB

f_ea_checks/14-Feb-20134 KiB

f_end-bitmap/14-Feb-20134 KiB

f_expand/14-Feb-20134 KiB

f_ext_journal/14-Feb-20134 KiB

f_extent_bad_node/14-Feb-20134 KiB

f_extents/14-Feb-20134 KiB

f_extents2/14-Feb-20134 KiB

f_extra_journal/14-Feb-20134 KiB

f_fast_symlink_extents/14-Feb-20134 KiB

f_file_acl_high/14-Feb-20134 KiB

f_filetype/14-Feb-20134 KiB

f_full_bg/14-Feb-20134 KiB

f_h_badnode/14-Feb-20134 KiB

f_h_badroot/14-Feb-20134 KiB

f_h_normal/14-Feb-20134 KiB

f_h_reindex/14-Feb-20134 KiB

f_h_unsigned/14-Feb-20134 KiB

f_holedir/14-Feb-20134 KiB

f_holedir2/14-Feb-20134 KiB

f_hurd/14-Feb-20134 KiB

f_illbbitmap/14-Feb-20134 KiB

f_illibitmap/14-Feb-20134 KiB

f_illitable/14-Feb-20134 KiB

f_illitable_flexbg/14-Feb-20134 KiB

f_imagic/14-Feb-20134 KiB

f_imagic_fs/14-Feb-20134 KiB

f_journal/14-Feb-20134 KiB

f_lotsbad/14-Feb-20134 KiB

f_lpf/14-Feb-20134 KiB

f_lpf2/14-Feb-20134 KiB

f_lpffile/14-Feb-20134 KiB

f_messy_inode/14-Feb-20134 KiB

f_miss_blk_bmap/14-Feb-20134 KiB

f_miss_journal/14-Feb-20134 KiB

f_misstable/14-Feb-20134 KiB

f_mke2fs2b/14-Feb-20134 KiB

f_noroot/14-Feb-20134 KiB

f_okgroup/14-Feb-20134 KiB

f_orphan/14-Feb-20134 KiB

f_orphan_dotdot_ft/14-Feb-20134 KiB

f_overfsblks/14-Feb-20134 KiB

f_preen/14-Feb-20134 KiB

f_recnect_bad/14-Feb-20134 KiB

f_reconnect/14-Feb-20134 KiB

f_rehash_dir/14-Feb-20134 KiB

f_resize_inode/14-Feb-20134 KiB

f_salvage_dir/14-Feb-20134 KiB

f_selinux/14-Feb-20134 KiB

f_special_ea/14-Feb-20134 KiB

f_summary_counts/14-Feb-20134 KiB

f_uninit_last_uninit/14-Feb-20134 KiB

f_unsorted_EAs/14-Feb-20134 KiB

f_unused_itable/14-Feb-20134 KiB

f_valid_ea_in_inode/14-Feb-20134 KiB

f_zero_group/14-Feb-20134 KiB

f_zero_inode_size/14-Feb-20134 KiB

f_zero_super/14-Feb-20134 KiB

filter_dumpe2fs14-Feb-2013321

m_dasd_bs/14-Feb-20134 KiB

m_large_file/14-Feb-20134 KiB

m_meta_bg/14-Feb-20134 KiB

m_mkfs_overhead/14-Feb-20134 KiB

m_no_opt/14-Feb-20134 KiB

m_raid_opt/14-Feb-20134 KiB

m_std/14-Feb-20134 KiB

m_uninit/14-Feb-20134 KiB

Makefile.in14-Feb-20132 KiB

mke2fs.conf.in14-Feb-2013831

progs/14-Feb-20134 KiB

r_inline_xattr/14-Feb-20134 KiB

r_move_itable/14-Feb-20134 KiB

r_resize_inode/14-Feb-20134 KiB

README14-Feb-20133 KiB

run_e2fsck14-Feb-20131.9 KiB

run_mke2fs14-Feb-2013595

test_config14-Feb-20131,021

test_script.in14-Feb-20131.6 KiB

u_mke2fs/14-Feb-20134 KiB

u_tune2fs/14-Feb-20134 KiB

README

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