From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: waxhead@dirtcellar.net, joshua <joshua@mailmag.net>,
Qu Wenruo <wqu@suse.com>
Cc: Remi Gauvin <remi@georgianit.com>,
dsterba@suse.cz, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Does btrfs filesystem defragment -r also include the trees?
Date: Sun, 23 Apr 2023 18:50:04 +0800 [thread overview]
Message-ID: <d44ed6bf-d8e4-a7aa-4713-72102f261bbe@gmx.com> (raw)
In-Reply-To: <1fbcdce2-a268-aa1d-1e6c-bb1e61e18ad9@dirtcellar.net>
On 2023/4/23 17:34, waxhead wrote:
>>
>> On 2023/4/22 07:25, joshua wrote:
>>> For my situation, (and others with large arrays) yes definitely.
>>> It's definitely the feature I'm most interested in patiently waiting
>>> for....
>>>
>>
>> You can already compile the current btrfs-progs release with
>> experimental features, which enables the "btrfstune -b" command to
>> convert your existing btrfs to the new feature.
>>
>> I believe David would release the next btrfs-progs with bg tree moved
>> to regular features.
>>
>> And even better, the new bg-tree feature is compat_ro, meaning
>> unsupported kernel can still mount the fs RO.
>>
>> Thanks,
>> Qu
>
> And for those of us that have BTRFS as root? Would we live happily ever
> after or would GRUB choke on this?
Compat_ro feature means, any implementation, which only does read-only
operations, would be fine.
Although for GRUB, I'm not that confident about their implementation...
Thanks,
Qu
prev parent reply other threads:[~2023-04-23 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 12:37 Does btrfs filesystem defragment -r also include the trees? Remi Gauvin
2023-04-20 22:42 ` David Sterba
2023-04-21 7:57 ` Qu Wenruo
2023-04-21 12:21 ` Remi Gauvin
2023-04-21 17:41 ` waxhead
2023-04-21 21:00 ` Forza
2023-04-21 21:27 ` Remi Gauvin
2023-04-21 21:40 ` joshua
2023-04-21 22:55 ` Qu Wenruo
2023-04-21 23:25 ` joshua
2023-04-22 0:42 ` Qu Wenruo
2023-04-23 9:34 ` waxhead
2023-04-23 10:50 ` Qu Wenruo [this message]
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=d44ed6bf-d8e4-a7aa-4713-72102f261bbe@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=joshua@mailmag.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.com \
--cc=waxhead@dirtcellar.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.