public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Christoph Anton Mitterer <calestyo@scientia.org>
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 6.19
Date: Tue, 17 Mar 2026 17:34:25 +0100	[thread overview]
Message-ID: <20260317163424.GY5735@twin.jikos.cz> (raw)
In-Reply-To: <ced007c60ff226a2988f388c9389c240c8057843.camel@scientia.org>

On Sat, Feb 14, 2026 at 03:18:51AM +0100, Christoph Anton Mitterer wrote:
> On Fri, 2026-02-13 at 19:56 +0100, David Sterba wrote:
> >   * make block-group-tree default (support since linux 6.1), use -O
> > ^bgt to
> >     unset it for backward compatibility
> 
> I guess that also mean that this is now considered stable and has been
> very well tested?

Yes, the bgt feature has been part of the fstests runs.

> How about migrating an existing fs to use the block-group-tree (with
> btrfstune --convert-to-block-group-tree)... has that also been well
> tested and is considered safe to be used on filesystems with precious
> data?

The in-place conversions are a bit more tricky as they start from an
existing filesystem and there's a possibility of finding some corner
case. Last time this was in 6.15.

It should be doable to test the conversion using device mapper snapshot
devices on an existing valuable filesystem without destroying it.

  reply	other threads:[~2026-03-17 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 18:56 Btrfs progs release 6.19 David Sterba
2026-02-14  2:18 ` Christoph Anton Mitterer
2026-03-17 16:34   ` David Sterba [this message]
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=20260317163424.GY5735@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=calestyo@scientia.org \
    --cc=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