From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: [ANNOUNCE] e2fsprogs v1.45.3
Date: Thu, 18 Jul 2019 11:21:57 -0400 [thread overview]
Message-ID: <20190718152157.GA25476@mit.edu> (raw)
I've released e2fsprogs 1.45.3 in all of the usual places; it's tagged
in the git trees on git.kernel.org, github, and sourceforge, and
available for download at:
http://www.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.45.3
and
http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.45.3.tar.gz
The release notes for 1.45.3 can be found below.
Cheers,
- Ted
E2fsprogs 1.45.3 (July 14, 2019)
================================
Updates/Fixes since v1.45.2:
UI and Features
---------------
Whether or not automatic online scrubs will be run is now controlled by
a setting in /etc/e2scrub.conf. To enable automatic online scrubs,
uncomment out the line containing "periodic_e2scrub=1".
The fuse2fs program is now installed in /usr/bin instead of /usr/sbin,
since it does not require root privileges.
Fuse2fs now works with if fusermount from FUSE V3 is installed.
However, in order to provide this compatibility, if you are using a
fusermount from FUSE v2, and you want to mount on top of a non-empty
directory, you will need to specify -o nonempty explicitly. FUSE V3
always allows mounting on top of non-empty directories, and will fail if
the user or fuse2fs passes the nonempty option.
Fixes
-----
Fixed a bug which caused e2fsck to improperly handle file systems that
enabled both the large_dir and inline directories at the same time.
E2scrub_all now correctly handles an encrypted (LUKS) ext[234] file
system stacked on top of an LVM volume. (Addresses Debian Bug: #931387)
Fixed a bug in "E2scrub_all -r" where it was incorrectly specifying
which volume needed to have its e2scrub snapshot cleaned up. (Addresses
Debian Bug: #931679)
Fixed the Czech, Dutch, German, and Vietnamese translations which
improperly used positional markers which broke a few translated e2fsck
problem descriptions. (Addresses Debian Bug: #892173)
Performance, Internal Implementation, Development Support etc.
--------------------------------------------------------------
Fixed various debian packaging issues. (Addresses Debian Bug: #931266,
#923372)
Fixed error checking for calls to posix_{memalign,fadvise}.
Add regression test for checking a file system using fs-verity.
Various regression test cleanups.
Fixed various compiler warnings.
Added xgettext markers to fix incorrectly marked strings in the
e2fsprogs translations template file as being c-style printf strings
when in fact they aren't.
Added utility script which generates the release tarfile using git
archive.
Update the Czech, Dutch, and Portuguese translations from the
Translation Project.
reply other threads:[~2019-07-18 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190718152157.GA25476@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).