From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.16
Date: Wed, 13 Aug 2025 20:10:50 +0200 [thread overview]
Message-ID: <20250813181054.9949-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 6.16 have been released.
This is more of a bugfix release again with some new updates.
Changelog:
* mkfs:
* print label of existing filesystem if attempting to overwrite
* remove note about changed defaults in 6.15
* discard support detection uses the ioctl and not sysfs, this should
work for all types of block devices
* device usage: fix printing units of partition sizes, used to be in 512B
sectors
* defrag: new option --nocomp to request no compression (kernel 6.17)
* check: detect missing orphan items for deleted subvolumes
* subvol delete: don't print warning if filesystem is mounted with
user_subvol_rm_allowed
* build: add build support for Android
* other:
* cleanups and refactoring
* sync sources with kernel
* documentation updates
* CI and test 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.16
Python: https://pypi.org/project/btrfsutil/
reply other threads:[~2025-08-13 18:11 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=20250813181054.9949-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