From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Boris Burkov <boris@bur.io>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 2/2] btrfs: automatically remove the subvolume qgroup
Date: Wed, 1 May 2024 07:57:08 +0930 [thread overview]
Message-ID: <d49e13f2-59ff-49ef-b81c-8c2c96d8284b@gmx.com> (raw)
In-Reply-To: <20240430221839.GA51927@zen.localdomain>
在 2024/5/1 07:48, Boris Burkov 写道:
> On Wed, May 01, 2024 at 07:35:09AM +0930, Qu Wenruo wrote:
[...]
>>>
>>> I don't see how a compat bit would work here, we use them for feature
>>> compatibility and for general access to data (full or read-only). What
>>> we do with individual behavioral changes are sysfs files. They're
>>> detectable by scripts and can be also used for configuration. In this
>>> case enabling/disabling autoclean of the qgroups.
>
> This was my initial thought too, but your compat bit idea is interesting
> since it persists? I vote sysfs since it has good
> infrastructure/momentum already for similar config.
Sysfs is another way which we are already utilizing for qgroups, like
drop_subtree_threshold.
The problem is as mentioned already, it's not persistent, thus it needs
a user space daemon to set it for every fs after mount.
I'm totally fine to go sysfs for now, but I really hope to a persistent
solution.
Maybe a dedicated config tree?
Thanks,
Qu
>
>>>
>>
>> I mean the compat bit, which is fully empty now.
>>
>> The new bit would be something like BTRFS_QGROUP_AUTO_REMOVAL, with that
>> set, btrfs would auto remove any stale qgroups (for regular qgroups though).
>>
>> Without that, it would be as usual (no auto removal).
>>
>> Since this doesn't cause any on-disk change, it does not needs compat-ro
>> nor incompat.
>>
>> Thanks,
>> Qu
next prev parent reply other threads:[~2024-04-30 22:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:46 [PATCH v2 0/2] btrfs: qgroup: stale qgroups related impromvents Qu Wenruo
2024-04-19 9:46 ` [PATCH v2 1/2] btrfs: slightly loose the requirement for qgroup removal Qu Wenruo
2024-04-29 12:47 ` Boris Burkov
2024-04-29 22:00 ` Qu Wenruo
2024-04-29 22:19 ` Boris Burkov
2024-04-29 22:29 ` Qu Wenruo
2024-04-29 22:38 ` Boris Burkov
2024-04-19 9:46 ` [PATCH v2 2/2] btrfs: automatically remove the subvolume qgroup Qu Wenruo
2024-04-24 12:41 ` David Sterba
2024-04-24 22:19 ` Qu Wenruo
2024-04-25 12:34 ` David Sterba
2024-04-25 21:51 ` Qu Wenruo
2024-04-29 13:13 ` Boris Burkov
2024-04-29 16:31 ` David Sterba
2024-04-29 22:05 ` Qu Wenruo
2024-04-30 10:59 ` David Sterba
2024-04-30 22:05 ` Qu Wenruo
2024-04-30 22:18 ` Boris Burkov
2024-04-30 22:27 ` Qu Wenruo [this message]
2024-05-02 15:03 ` David Sterba
2024-05-02 21:29 ` Qu Wenruo
2024-05-03 12:46 ` David Sterba
2024-05-03 22:14 ` Qu Wenruo
2024-05-02 15:00 ` David Sterba
2024-05-02 21:27 ` Qu Wenruo
2024-04-29 22:49 ` Qu Wenruo
2024-04-29 16:36 ` David Sterba
2024-04-29 12:57 ` Boris Burkov
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=d49e13f2-59ff-49ef-b81c-8c2c96d8284b@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=boris@bur.io \
--cc=dsterba@suse.cz \
--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