public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.19
Date: Fri, 13 Feb 2026 19:56:46 +0100	[thread overview]
Message-ID: <20260213185647.21966-1-dsterba@suse.com> (raw)

Hi,

btrfs-progs version 6.19 have been released (ther version 6.18 has been skipped).

There's change in mkfs.btrfs defaults, the block group tree is now enabled. A
note is printed (which was a last minute change and the release was redone, the
top commit is 9ac9a97ee3ebcc71).

Changelog:

* mkfs:
  * make block-group-tree default (support since linux 6.1), use -O ^bgt to
    unset it for backward compatibility
  * speed up initial device discard by procesing the ranges in order
  * disable block-grooup-tree feature if a dependent feature is explicitly
    unselected (like disabling no-holes), instead of erroring out
* check:
  * add ability to detect and fix missing orphan items in deleted subvolumes
  * add ability to fix inode refs from directory items
  * enhance detection on unknown inode keys
* libbtrfsutil:
  * minor version update to 1.4.0
  * add missing aliases for API updates done in 0.1.3, C and python
* libbtrfs:
  * patchlevel version update 0.1.5
  * error handling updates
* fixes:
  * with DUP profile and mixed sequential and conventional zoned make sure
    to track the right write pointers
  * scrub: fix ETA wraparound calculations, when many files get deleted
    during the operation bytes_scrubbed and bytes_total get too much out of
    sync, the ETA will be 0
* corrupt-block: add ability to specify key value when corrupting item keys
* experimental features:
  * initial remap tree support (new logical-to-logical mapping layer),
    coming in linux 7.0
* other:
  * documentation updates
  * CI updates, new and updated tests
  * code cleanups and refactoring

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.19
Python: https://pypi.org/project/btrfsutil/

             reply	other threads:[~2026-02-13 18:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 18:56 David Sterba [this message]
2026-02-14  2:18 ` Btrfs progs release 6.19 Christoph Anton Mitterer
2026-03-17 16:34   ` David Sterba
2026-03-25  0:49     ` Christoph Anton Mitterer
2026-03-25  4:18       ` joshua
2026-03-25 16:21         ` Christoph Anton Mitterer
2026-03-26  0:31           ` joshua

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