From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] btrfs-progs: cmds/qgroup: enhance stale qgroups handling
Date: Fri, 17 May 2024 18:15:38 +0200 [thread overview]
Message-ID: <20240517161538.GC17126@twin.jikos.cz> (raw)
In-Reply-To: <cover.1715245781.git.wqu@suse.com>
On Thu, May 09, 2024 at 06:42:29PM +0930, Qu Wenruo wrote:
> Currently the `<stale>` label is give incorrectly for a lot of qgroups
> that can not and should not be deleted.
>
> The patchset would address the problem for `btrfs qgroup show` and
> `btrfs qgroup clear-stale` commands, so that:
>
> - `clear-stale` would not try to delete incorrect qgroups
> Thus it should not return false errors.
>
> - `show` would show extra types of qgroups
> Including `<under deletion>` and `<squota space holder>`
>
> Qu Wenruo (4):
> btrfs-progs: cmds/qgroup: sync the fs before doing qgroup search
> btrfs-progs: cmds/qgroup: add qgroup_lookup::flags member
> btrfs-progs: cmds/qgroup: handle stale qgroup deleteion more
> accurately
> btrfs-progs: cmds/qgroup: add more special status for qgroups
Added to devel, thanks. Please use the subjects that match the style
used in progs, ie. no 'cmds/' prefix.
prev parent reply other threads:[~2024-05-17 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 9:12 [PATCH 0/4] btrfs-progs: cmds/qgroup: enhance stale qgroups handling Qu Wenruo
2024-05-09 9:12 ` [PATCH 1/4] btrfs-progs: cmds/qgroup: sync the fs before doing qgroup search Qu Wenruo
2024-05-09 9:12 ` [PATCH 2/4] btrfs-progs: cmds/qgroup: add qgroup_lookup::flags member Qu Wenruo
2024-05-09 9:12 ` [PATCH 3/4] btrfs-progs: cmds/qgroup: handle stale qgroup deleteion more accurately Qu Wenruo
2024-05-09 9:12 ` [PATCH 4/4] btrfs-progs: cmds/qgroup: add more special status for qgroups Qu Wenruo
2024-05-17 16:15 ` David Sterba [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=20240517161538.GC17126@twin.jikos.cz \
--to=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