From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.9
Date: Fri, 7 Jun 2024 17:59:20 +0200 [thread overview]
Message-ID: <20240607155922.14362-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 6.9 have been released.
Mostly bug fixes, libraries have been updated and are backward compatible.
Changelog:
* mkfs:
* if --force used, don't continue if the mount status cannot be
determined (e.g. due to permissions)
* fix minimum size calculation on zoned devices, make it work with option -b
* check:
* option --clear-ino-cache removed (functionality still provided in
'rescue' command group)
* detect and repair wrong file extent item ram_bytes value
* qgroup clear-stale:
* sync the filesystem before search to read the up to date state
* handle cases where qgroup cannot be deleted due to uncleaned subvolume
or when squota is enabled
* qgroup show: display status of qgroup regarding the cleaning of the
subvolume or if it's squota
* receive: fix stream parsing on strict alignment hosts (e.g. ARM v5 or v6)
* tune change-csum: fix check of dev-replace status item, continue if no
dev-replace in progress
* dump-tree: print contents of dev-replace status item
* convert: fix extent iteration to handle prealloc/unwritten extents
* libbtrfsutil:
* patchlevel version update 1.3.1
* fix potentially unaligned access to send stream
* create library links to all version levels
* libbtrfs:
* patchlevel version update 0.1.3
* fix potentially unaligned access to send stream
* create library links to all version levels
* build:
* fix compatibility with e2fsprogs 1.47.1
* fix header file dependency tracking
* -O2 by default
* other:
* new and updated tests
* ASAN and UBSAN test coverage in CI
* documentation updates
Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
Release: https://github.com/kdave/btrfs-progs/releases/tag/v6.9
reply other threads:[~2024-06-07 15:59 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=20240607155922.14362-1-dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@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