doc/RelNotes/v1.08.txt

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