From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 7.1
Date: Wed, 15 Jul 2026 00:54:04 +0200 [thread overview]
Message-ID: <20260714225407.688358-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 7.1 have been released.
Changelog:
* mkfs:
* use GET_CSUMS ioctl (if provided by kernel, 7.2) to reuse existing
checksums for --rootdir, works with --reflink to avoid reading file data
* fix last block handling for reflink
* fix handling of incompressible data extents
* fix --rootdir size estimation when using hardlinks
* fi mkswapfile: add option to specify page size, useful on ARM64
* check: add option to skip qgroup verification to speed up check
* in experimental build, use V2 of tree search ioctl, this can use larger
buffer
* preliminary fscrypt support
* enhance filesystem opening modes with more fine-grained support of
partially damaged trees and allow to skip non-essential trees
* other:
* stability and error handling fixes
* CI updates
* updated tests
* 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/v7.1
Python: https://pypi.org/project/btrfsutil/
reply other threads:[~2026-07-14 22:54 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=20260714225407.688358-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