From d050855585ab3cdf0a49507f78f0bfc35e68c17a Mon Sep 17 00:00:00 2001
From: tytso The mke2fs and e2fsck now use significantly less memory when creating
+or checking very large file systems. This was enabled by adding
+extent-based bitmaps which are stored using a red-block tree, since
+block and inode allocations tend to be contiguous. The command mke2fs -S is used as a last ditch recovery command to
+write new superblock and block group descriptors, but _not_ to destroy
+the inode table in hopes of recovering from a badly corrupted file
+system. So if the uninit_bg feature is enabled, mke2fs -S will now
+set the unused inodes count field to zero. Otherwise, e2fsck -fy
+after using mke2fs -S would leave the file system completely empty. Since mke2fs recognizes mke3fs in argv[0] to mean "mkfs.ext3", also
+honor "mke4fs" to work the same as "mke2fs.ext4", since RHEL5 has
+installed an mke2fs binary using that name. The usage and help messages for the -G, -t and -T options in mke2fs
+have been fixed. If e2fsck needs to use the backup group descriptors, the
+ext2fs_open2() function clears the UNINIT bits to ensure all of the
+inodes in the file systems get scanned. However, the code which reset
+the UNINIT flags did not also recalculate the checksum, which produced
+many spurious (and scary) e2fsck messages. This has been fixed by
+resetting cheksums when the UNINIT bits are cleared. Relax a check in e2fsck which required that the block bitmap to be
+initialized when the inode bitmap is in use. This will allow us to
+eventually eliminate code from the kernel which forcibly initialized
+the block bitmap when the inode bitmap is first used, requiring an
+extra journal credit and disk write. (Addresses Google Bug: #5944440) Make sure rdebugfs (which may be installed setuid or setgid disk) does
+not honor environment variables if euid != uid or egid != gid. Debugfs's ncheck command has been optimized and now is much more
+robust with faced with corrupted file systems. The ncheck command
+also now has a -c option which will verify the file type information
+in the directory entry to see if matches the inode's mode bits. This
+is extremely useful when trying to use debugsfs to determine which
+parts of the file system metadata can be trusted. E2image will try to use ftruncate64() to set the i_size for raw
+images, instead of writing a single null byte. This avoid allocating
+an extra block to the raw image, for those file systems and/or
+operating systems that support this. (Linux does.) In addition, fix
+a logic bug that caused the file to not be properly extended if the
+size of the last hole was exactly an multiple of a megabyte. Fixed a bug in resize2fs where for 1k and 2k file systems, where
+s_first_data_block is non-zero, this wasn't taken into account when
+calculate the minimum file system size for use with the -M option. Fixed the badblocks program to honor the -s flag when in read-only -t
+mode. (Addresses Debian Bug #646629) Update Czech, Dutch, French, Polish, and Sweedish translation from the
+Translation Project. Fixed various Debian Packaging issues so that dpkg-buildflags is used
+if present, which allows e2fsprogs to be built with security hardening
+flags. (Addresses Debian Bugs: #654457) Fix a bug in ext2fs_clear_generic_bmap() when used for 32-bit bitmaps.
+This was only an issue for programs compiled against e2fsprogs 1.41
+that manipulate bitmaps directly. (Addresses Sourceforge Bugs:
+#3451486) The libext2fs library now uses sysconf() to fetch the page size, instead
+of the deprecated getpagesize(). The ext2fs_get_pathname() function will return a partial path if an a
+directory in the path is not a directory, displaying it as an inode
+number in angle brackets instead of giving up and displaying an error.
+This is much more helpful when a user is trying to debug a corrupted
+file system. Codepoints for the RO_COMPAT_REPLICA feature has been reserved. Added a new library function, ext2fs_file_get_inode_num(), for use by
+fuse2fs. Fixed a bug in ext2fs_file_set_size2() so that when it is truncating a
+file, it actually works. The block iterator now properly honors the BLOCK_ABORT flag for
+extent-based flags. Previously, it didn't, which generally made code
+be less efficient, but it could cause bugs in ext2fs_link(), for
+example, by causing it to insert multiple directory entries. Fixed an (harmless other than causing a compiler warning) use of an
+uninitialized variable in e2fsck's MMP code. This release of e2fsprogs has support for file systems > 16TB. Online
diff --git a/htdocs/ext2.html b/htdocs/ext2.html
index 5f60ff713..ed4d27cd8 100644
--- a/htdocs/ext2.html
+++ b/htdocs/ext2.html
@@ -28,9 +28,9 @@
On November 29, 2010, version 1.42 of e2fsprogs was On February 17, 2012, version 1.42.1 of e2fsprogs was announced.Release notes for the e2fsprogs package
+
+E2fsprogs 1.42.1 (February 17, 2011)
+
+Programmer's Notes
+
+E2fsprogs 1.42 (November 29, 2011)
-
Release 1.42 of e2fsprogs is available!
+Release 1.42.1 of e2fsprogs is available!
-Ext2fs Utilities
diff --git a/htdocs/index.html b/htdocs/index.html
index c978046e8..1ce45c54f 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -34,12 +34,12 @@
here.
I am happy to announce a new release of the e2fsprogs distribution. - All users of e2fsprogs are urged to upgrade to the 1.42 version as - soon as possible, which can be found here.
+ All users of e2fsprogs are urged to upgrade to the 1.42.1 version as + soon as possible, which can be found here.This release contains a number of bug fixes and enhancements over the previous releases. For more details, see the -- 2.47.2