From: Nicholas D Steeves <nsteeves@gmail.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] btrfs-progs: add block-group-tree to the default mkfs/convert features
Date: Mon, 01 Dec 2025 20:21:11 -0500 [thread overview]
Message-ID: <87o6ohisqg.fsf@gmail.com> (raw)
In-Reply-To: <cover.1764228560.git.wqu@suse.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
Hi Qu,
Qu Wenruo <wqu@suse.com> writes:
> [CHANGELOG]
> v2:
> - Automatically remove bgt feature when dependent feature is missing
> Instead of erroring out. This will allow us to run the existing
> no-holes/v1 free space cache test cases without any modification.
>
> I was planning to do this during v6.12 but forgot it and now the next
> LTS kernel release is not that far away, it's finally time to make the
> switch.
>
Does this also mean that block-group-tree is considered recommended and
production-ready for users of linux-6.12 LTS, or that it will only be
recommended for the next LTS kernel series?
Also, are there any known disadvantages that result from having used
btrfstune compared with a pristine FS created with
mkfs.btrfs -O block-group-tree ?
Best,
Nicholas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2025-12-02 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 7:33 [PATCH v2 0/3] btrfs-progs: add block-group-tree to the default mkfs/convert features Qu Wenruo
2025-11-27 7:33 ` [PATCH v2 1/3] btrfs-progs: disable block-group-tree feature if dependency is missing Qu Wenruo
2025-11-27 7:33 ` [PATCH v2 2/3] btrfs-progs: misc-tests: check if free space tree is enabled after mount Qu Wenruo
2025-11-27 7:33 ` [PATCH v2 3/3] btrfs-progs: add block-group-tree to the default mkfs features Qu Wenruo
2025-12-02 1:21 ` Nicholas D Steeves [this message]
2025-12-02 4:09 ` [PATCH v2 0/3] btrfs-progs: add block-group-tree to the default mkfs/convert features Qu Wenruo
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=87o6ohisqg.fsf@gmail.com \
--to=nsteeves@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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