Home | History | Annotate | only in /external/e2fsprogs/tests
Up to higher level directory
NameDateSize
d_loaddump/10-Jul-2012
defaults/10-Jul-2012
e_brel_bma/10-Jul-2012
e_icount_normal/10-Jul-2012
e_icount_opt/10-Jul-2012
e_irel_ima/10-Jul-2012
f_16384_block/10-Jul-2012
f_8192_block/10-Jul-2012
f_bad_disconnected_inode/10-Jul-2012
f_bad_local_jnl/10-Jul-2012
f_badbblocks/10-Jul-2012
f_baddir/10-Jul-2012
f_baddir2/10-Jul-2012
f_baddotdir/10-Jul-2012
f_badinode/10-Jul-2012
f_badjour_indblks/10-Jul-2012
f_badjourblks/10-Jul-2012
f_badorphan/10-Jul-2012
f_badprimary/10-Jul-2012
f_badroot/10-Jul-2012
f_badsymlinks/10-Jul-2012
f_badtable/10-Jul-2012
f_bbfile/10-Jul-2012
f_bbinode/10-Jul-2012
f_big_sparse/10-Jul-2012
f_bitmaps/10-Jul-2012
f_clear_xattr/10-Jul-2012
f_crashdisk/10-Jul-2012
f_dir_bad_mode/10-Jul-2012
f_dirlink/10-Jul-2012
f_dup/10-Jul-2012
f_dup2/10-Jul-2012
f_dup3/10-Jul-2012
f_dup4/10-Jul-2012
f_dup_de/10-Jul-2012
f_dup_de2/10-Jul-2012
f_dup_resize/10-Jul-2012
f_dupdot/10-Jul-2012
f_dupfsblks/10-Jul-2012
f_dupsuper/10-Jul-2012
f_ea_checks/10-Jul-2012
f_end-bitmap/10-Jul-2012
f_expand/10-Jul-2012
f_ext_journal/10-Jul-2012
f_extent_bad_node/10-Jul-2012
f_extents/10-Jul-2012
f_extents2/10-Jul-2012
f_extra_journal/10-Jul-2012
f_fast_symlink_extents/10-Jul-2012
f_file_acl_high/10-Jul-2012
f_filetype/10-Jul-2012
f_full_bg/10-Jul-2012
f_h_badnode/10-Jul-2012
f_h_badroot/10-Jul-2012
f_h_normal/10-Jul-2012
f_h_reindex/10-Jul-2012
f_h_unsigned/10-Jul-2012
f_holedir/10-Jul-2012
f_holedir2/10-Jul-2012
f_hurd/10-Jul-2012
f_illbbitmap/10-Jul-2012
f_illibitmap/10-Jul-2012
f_illitable/10-Jul-2012
f_illitable_flexbg/10-Jul-2012
f_imagic/10-Jul-2012
f_imagic_fs/10-Jul-2012
f_journal/10-Jul-2012
f_lotsbad/10-Jul-2012
f_lpf/10-Jul-2012
f_lpf2/10-Jul-2012
f_lpffile/10-Jul-2012
f_messy_inode/10-Jul-2012
f_miss_blk_bmap/10-Jul-2012
f_miss_journal/10-Jul-2012
f_misstable/10-Jul-2012
f_mke2fs2b/10-Jul-2012
f_noroot/10-Jul-2012
f_okgroup/10-Jul-2012
f_orphan/10-Jul-2012
f_orphan_dotdot_ft/10-Jul-2012
f_overfsblks/10-Jul-2012
f_preen/10-Jul-2012
f_recnect_bad/10-Jul-2012
f_reconnect/10-Jul-2012
f_rehash_dir/10-Jul-2012
f_resize_inode/10-Jul-2012
f_salvage_dir/10-Jul-2012
f_selinux/10-Jul-2012
f_special_ea/10-Jul-2012
f_summary_counts/10-Jul-2012
f_swapfs/10-Jul-2012
f_uninit_last_uninit/10-Jul-2012
f_unsorted_EAs/10-Jul-2012
f_valid_ea_in_inode/10-Jul-2012
f_zero_group/10-Jul-2012
f_zero_inode_size/10-Jul-2012
f_zero_super/10-Jul-2012
filter_dumpe2fs10-Jul-2012321
m_dasd_bs/10-Jul-2012
m_large_file/10-Jul-2012
m_meta_bg/10-Jul-2012
m_mkfs_overhead/10-Jul-2012
m_no_opt/10-Jul-2012
m_raid_opt/10-Jul-2012
m_std/10-Jul-2012
m_uninit/10-Jul-2012
Makefile.in10-Jul-20122K
progs/10-Jul-2012
r_inline_xattr/10-Jul-2012
r_move_itable/10-Jul-2012
r_resize_inode/10-Jul-2012
README10-Jul-20123K
run_e2fsck10-Jul-20121.9K
run_mke2fs10-Jul-2012595
test_config10-Jul-20121,021
test_script.in10-Jul-20121.6K
u_mke2fs/10-Jul-2012
u_tune2fs/10-Jul-2012

README

      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
     66 symlinks.img		Filesystem with bad symlink sizes
     67 
     68 
     69