1E2fsprogs 1.08 (April 10, 1997)
2===============================
3
4E2fsck 1.07 was very slow when checking very large filesystems with a
5lot of files that had hard links (i.e., news spools).  This was fixed
6by seriously revamping the icount abstraction.  Added a formal test
7suite for the icount abstraction.
8
9Debugfs now has a "-l" option to the "ls" command, which lists the
10inode number, permissions, owner, group, size, and name of the files
11in the directory.
12
13Fix a bug in e2fsck where when a directory had its blocks moved to
14another location during the pass 1b processing, the directory block
15list wasn't updated, so pass 2 wouldn't check (and correct) the
16correct directory block.
17
18E2fsck will now treat inodes which contain blocks which are claimed by
19the filesystem metadata by treating them as multiply claimed blocks.
20This way, the data in those blocks can be copied to a new block during
21the pass 1b--1d processing.
22
23E2fsck will attempt to determine the correct superblock number and
24display it in the diagnostic and warning messages if possible.
25
26Add support for a new (incompatible) feature, "sparse_super".  This
27feature reduces the number of blocks which contain copies of backup
28superblocks and block group descriptors.  (It is only an incompatible
29feature because of a bug in ext2_free_blocks.)  mke2fs and tune2fs now
30support a new -s option; e2fsck will recognize filesystems built with
31this feature turned on.
32
33E2fsck now checks the library to make sure is the correct version,
34using new library functions.  (This helps to diagnose incorrectly
35installed e2fsprogs distributions.)
36
37Dumpe2fs now prints more information; its now prints the the
38filesystem revision number, the filesystem sparse_super feature (if
39present), the block ranges for each block group, and the offset from
40the beginning of the block group.
41
42Mke2fs now distributes the inode and block bitmap blok so that the
43won't be concentrated in one or two disks in RAID/striping setups.
44Also, if the user chooses a 2k or 4k block group, mke2fs will try to
45choose the largest blocks per group that be chosen.  (For 2k blocks,
46you can have up to 16384 blocks/group; for 4k blocks, you can have up
47to 32768 blocks/group.)  Previously mke2fs would not allow
48specification of more than 8192 blocks per group, even if you were
49using a 2k or 4k block group.
50
51Programmer's notes:
52-------------------
53
54Added a new function ext2fs_create_icount2() which takes a "hint"
55argument.  This hint argument presets the icount array with the list
56of inodes which actually need to be in the icount array.  This really
57helps to speed up e2fsck.
58
59Added a new function ext2fs_icount_validate() which checks the rep
60invariant for the icount structure.  This is used mostly for testing.
61
62The error message given when a bad inode number is passed to
63test_generic_bitmap to reflect EXT2FS_TEST_ERROR (instead of
64EXT2FS_UNMARK_ERROR).
65
66Added a new function ext2fs_set_dir_block which sets the block of a
67dblist entry, given the directory inode and blockcnt.
68
69Added a new function ext2fs_get_library_version() which returns the
70current library version, and ext2fs_parse_version_string() which
71returns a version number based on a e2fsprogs version string.
72
73The icount functions will return EINVAL if the passed in inode number
74is out of bounds.
75
76