projects / thirdparty / e2fsprogs.git / blame
| Commit | Line | Data |
|---|---|---|
| 899425bb TT |
1 | E2fsprogs 1.44.0 (February 27, 2018) |
| 2 | ==================================== | |
| 3 | ||
| 4 | Updates/Fixes since v1.43.9: | |
| 5 | ||
| 6 | UI and Features | |
| 7 | --------------- | |
| 8 | ||
| 9 | E2fsprogs now supports the large_dir (INCOMPAT_LARGEDIR) feature. This | |
| 10 | feature allows larger directories to be created, both with directory | |
| 11 | sizes over 2GB and and a maximum htree depth of 3 instead of the | |
| 12 | current limit of 2. These features are needed in order to exceed | |
| 13 | the currently limit of approximately 10M entries in a single | |
| 14 | directory for 4KB blocksize (~100k for 1KB). | |
| 15 | ||
| 16 | E2fsprogs now supports the ea_inode (INCOMPAT_EA_INODE) feature, which | |
| 17 | stores large extended attributes in an external inode instead of a | |
| 18 | single data block. This is backwards compatible with a Lustre file | |
| 19 | system feature, but it has been extended to support deduplicating | |
| 20 | extended attribute values which are used in multiple inodes. | |
| 21 | ||
| 22 | The metadata_csum feature (RO_COMPAT_METADATA_CSUM) is now enabled by | |
| 23 | default by mke2fs. | |
| 24 | ||
| 25 | The resize2fs program will no longer complain about resizing bigalloc | |
| 26 | file systems as being dangerous when doing an on-line resize (since this | |
| 27 | is purely a kernel feature). | |
| 28 | ||
| 29 | Debugfs's ls command will now print the high bits of the inode's mode | |
| 30 | bits. | |
| 31 | ||
| 32 | Fixes | |
| 33 | ----- | |
| 34 | ||
| 35 | Fixed some potential buffer overrun bugs in the blkid library and in the | |
| 36 | fsck program. | |
| 37 | ||
| 38 | There were some corner cases which tune2fs wouldn't correctly handle | |
| 39 | when operating on a file system which was not cleanly mounted and thus | |
| 40 | required running the journal because it could be modified. Tune2fs will | |
| 41 | now run the journal before trying to change the superblock, and if the | |
| 42 | file system needs to be checked after the journal has been replayed, it | |
| 43 | will require it before proceeding. Also if the file system is busy (for | |
| 44 | example, because it is in use by Lustre), but is not present in the | |
| 45 | /proc/mounts or /etc/mtab, tune2fs will not try to replay the journal, | |
| 46 | since this could do real damage if it the file system is being actively | |
| 47 | modified by the kernel. | |
| 48 | ||
| 49 | The libss library (used by debugfs) now supports the version 7 of the | |
| 50 | libreadline shared library. | |
| 51 | ||
| 52 | The e2freefrag program will use the GETFSMAP ioctl if it is available | |
| 53 | and the file system is mounted, so that the free space statistics will | |
| 54 | be more accurate. | |
| 55 | ||
| c8c41d48 TT |
56 | The consistency checks for symlinks (especially for encrypted and inline |
| 57 | data file sytems) in e2fsck are now much more careful/stringent. Also | |
| 58 | fixed a bug where creating a symlink using ext2fs_symlink() which was | |
| 59 | exactly 60 bytes long when inline data was enabled would result in a | |
| 60 | missing system.data xattr. | |
| 61 | ||
| 899425bb TT |
62 | |
| 63 | Performance, Internal Implementation, Development Support etc. | |
| 64 | -------------------------------------------------------------- | |
| 65 | ||
| 66 | Mke2fs now uses io_channel_flush() instead of sync() for the sync_kludge | |
| 67 | feature. | |
| 68 | ||
| 69 | E2fsprogs now uses i_size as the primary way of determining whether a | |
| 70 | symlink is a fast symlink. | |
| 71 | ||
| 72 | Fix various compiler and UBSAN warnings. | |
| 73 | ||
| 74 | Long running test are now skipped with "make check" and only run when | |
| 75 | "make fullcheck". The test runner will warn when potentially long | |
| 76 | running tests are being run via "make check". | |
| 77 | ||
| 78 | E2fsck is now much faster for bigalloc file systems when scanning | |
| 79 | extents for bigalloc file systems. (Addresses Google Bug #36886699) |