From: Christoph Anton Mitterer <calestyo@scientia.org>
To: joshua <joshua@mailmag.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 6.19
Date: Wed, 25 Mar 2026 17:21:04 +0100 [thread overview]
Message-ID: <032be7a912897f0cf5ee90f3e5ee0b2c690ff76c.camel@scientia.org> (raw)
In-Reply-To: <2A0C37E0-28BD-4829-9778-AB20F4482F6D@mailmag.net>
On Tue, 2026-03-24 at 21:18 -0700, joshua wrote:
> For what it’s worth, (not much) I used --convert-to-block-group-tree
> on a large fs with precious data (~10 drives, ~100Tb, Raid1 data,
> Raid1C3 metadata) and had no issues.
>
> Convert took a LONG time, but afterwards, all my data integrity
> checks passed, scrub passed, and mount times are approximately 1
> second now, compared to minutes previously.
Thanks for the information. How long have you been running with it?
Cheers,
Chris.
next prev parent reply other threads:[~2026-03-25 16:30 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
2026-03-25 0:49 ` Christoph Anton Mitterer
2026-03-25 4:18 ` joshua
2026-03-25 16:21 ` Christoph Anton Mitterer [this message]
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=032be7a912897f0cf5ee90f3e5ee0b2c690ff76c.camel@scientia.org \
--to=calestyo@scientia.org \
--cc=joshua@mailmag.net \
--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