Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.16.1
Date: Wed, 10 Sep 2025 19:50:06 +0200	[thread overview]
Message-ID: <20250910175007.23176-1-dsterba@suse.com> (raw)

Hi,

btrfs-progs version 6.16.1 have been released. This is a minor feature update
(mkfs.btrfs) and bugfix release.

Changelog:

* mkfs:
   * add option --reflink, when used with --rootdir clone file extents instead
     of copying (requires source and target image on the same filesystem)
   * improved tracking of inodes and subvolumes for option --inode-flags
   * fix initializing raid-stripe-tree
   * extend what is trimmed/discarded during initialization (temporary chunks,
     free space)
* check: detect duplicate file names in directory items
* inspect tree-stats: accept string names for option -t
* receive: allow to dump stream from different user
* other:
   * updated documentation
   * new and updated tests

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.1

             reply	other threads:[~2025-09-10 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 17:50 David Sterba [this message]
2025-09-17 15:41 ` Btrfs progs release 6.16.1 Filipe Manana
2025-09-18  0:33   ` David Sterba
2025-09-18  5:10     ` Mark Harmstone
2025-09-18 12:17       ` Filipe Manana
2025-09-18 13:05         ` Mark Harmstone
2025-09-21 18:25           ` Chris Murphy
2025-09-21 18:32             ` Chris Murphy

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=20250910175007.23176-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