From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] e2fsprogs: Update to version 1.46.5
Date: Mon, 03 Jan 2022 12:59:24 +0000 [thread overview]
Message-ID: <2361D990-ED99-43DB-B7EB-0CA79D64B750@ipfire.org> (raw)
In-Reply-To: <20220103124529.3567992-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 6684 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 3 Jan 2022, at 12:45, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Update from 1.46.3 to 1.46.5
> - Update of rootfile not required
> - Changelog
> 1.46.5 (December 30, 2021)
> Updates/Fixes since v1.46.4:
> UI and Features
> When resizing a file system and the inode count exceeds the 2**32
> maximum, if resize2fs can successfully perform the resize by dropping
> the last block group, resize2fs will do that in order to allow the file
> system grow operation to succeed. For example, using the default inode
> ratio size of 16k, this will allow a successful resize to 64TB - 128MB
> when the storage device is 64TB.
> Fixes
> Avoid a potential infinite loop in resize2fs -P when the file system is
> corrupted (introduced in e2fsprogs 1.45.5). (Addresses github issue
> https://github.com/tytso/e2fsprogs/issues/94)
> E2fsck now updates the bg_checksum after fixing problems in the block
> group descriptor, which eliminates some unnecessary messages printed or
> asked of the system administrator.
> Fixed some potential deadlock problems in the unix_io handler in the case
> of I/O errors. The fix should also improve the performance of parallel
> bitmap loading.
> Fixed e2fsck's fast commit handling which could result it in crashing
> when trying to merge extents when there were none available to be
> merged.
> Fix e2fsck's support of quota limit data, which could sometimes get
> dropped when the quota data needs to be regenerated, or when processing
> the orphan list.
> Fix tune2fs to correctly transfer the quota limits when converting quota
> files to the internal quota inodes. Also add support for tune2fs to
> properly handle the older version 0 quota files.
> Fix debugfs's get_quota and list_quota commands so that the header of
> the report printed by these commands correctly reflect that the units of
> used space is in bytes instead of blocks.
> Performance, Internal Implementation, Development Support etc.
> Add some additional packages to the setup-schroot script to account for
> the fact that the script can be run on older Debian distributions and so
> the build dependencies might omit some packages needed to build
> e2fsprogs on unstable version of Debian.
> Reduce resize2fs's CPU overhead when counting the number of blocks in
> use which can reduce the wall clock time for very large file systems
> by substantial amount.
> Teach libuuid to use getrandom() or getentropy() if available in favor
> of reading from /dev/[u]random.
> Teach libss to use libreadline.so.8 if it is available.
> Update some test expect files to fix some regression tests that were
> broken in e2fsprogs 1.46.4.
> If the PRINT_FAILED environment variable is set, failed tests will
> display the diff output to make it easier to debug test failures on
> autobuilders.
> Fix various compiler warnings.
> Update tst_getsize to use ext2fs_get_size2() to support testing devices
> which are larger than 2**32 sectors.
> Fixed spelling mistakes in the mke2fs.conf man page.
> Update Chinese, Malay, Serbian, Spanish, Swedish, and Ukrainian
> translations.
> 1.46.4 (August 18, 2021)
> Updates/Fixes since v1.46.3:
> UI and Features
> The defaults for mke2fs now call for 256 byte inodes for all file
> systems (with the exception of file systems for the GNU Hurd, which only
> supports 128 byte inodes). Creating non-Hurd file systems with 128 byte
> inodes will trigger a warning message to make sure users are aware of
> the potential problems of using small/legacy inode sizes.
> The bigalloc feature is now considered supported if the cluster size no
> more than 16 times the block size. So the mke2fs program has been
> changes to only warn if the cluster size is larger than that.
> Fixes
> E2fsck now checks to make sure directory entries do not reference
> internal quota inodes.
> E2image now includes the quota inodes when creating file system image,
> since they are part of the file system metadata.
> E2fsck now properly accounts the quota usage of the project quota file.
> Fix a regression introduced in 1.64.3 where attempting to create a file
> system image using mke2fs into a non-existent file would fail.
> (Addresses Debian Bug: #992094)
> Fix mke2fs to correctly create Posix ACL's on big-endian systems when
> copying files from a directory hierarchy.
> Updated and clarified the resize2fs man page. (Addresses Debian Bug:
> #979411)
> Performance, Internal Implementation, Development Support etc.
> Improve various regression tests to be more portable and to reflect the
> new default inode size of 256 byte inodes, even for small file systems.
> Fixed a GNU Hurd portability problem which was causing tests to fail.
> Fixed a test failure in f_baddotdir on big-endian systems. This wasn't
> necessarily a bug per se in e2fsck, but rather e2fsck having different
> behaviour on big-endian systems. (Addresses Debian Bug: #991922)
> Use WantedBy=multi-user.target in e2scrub_reap.service. (Addresses
> Debian Bug: #991349)
> Synchronize e2fsck/recovery.c with the kernel's fs/jbd2/recovery.c
> Fix various Coverity and compiler warnings.
> Fix various error pathes to make sure we don't leak resources or
> potentially use or try to free uninitialized pointers.
> Added a setup-schroot command for use on Debian porter boxes.
> Updated config.guess and config.sub with newer versions from the FSF.
> Update Czech, Dutch, French, Polish, Portuguese, and Swedish translations.
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/e2fsprogs | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/e2fsprogs b/lfs/e2fsprogs
> index f417b77f4..64786860c 100644
> --- a/lfs/e2fsprogs
> +++ b/lfs/e2fsprogs
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.46.3
> +VER = 1.46.5
>
> THISAPP = e2fsprogs-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = ab7e15cafcd34681db907d3fcb395f95
> +$(DL_FILE)_MD5 = bb7d0c212dd99affa5fc512a3c7a949b
>
> install : $(TARGET)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2022-01-03 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 12:45 Adolf Belka
2022-01-03 12:59 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2361D990-ED99-43DB-B7EB-0CA79D64B750@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox