linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs-progs: cmds/qgroup: enhance stale qgroups handling
Date: Thu,  9 May 2024 18:42:29 +0930	[thread overview]
Message-ID: <cover.1715245781.git.wqu@suse.com> (raw)

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

 Documentation/btrfs-qgroup.rst |  24 +++++
 cmds/qgroup.c                  | 160 ++++++++++++++++++++++++++++-----
 2 files changed, 162 insertions(+), 22 deletions(-)

--
2.45.0


             reply	other threads:[~2024-05-09  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09  9:12 Qu Wenruo [this message]
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 ` [PATCH 0/4] btrfs-progs: cmds/qgroup: enhance stale qgroups handling David Sterba

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=cover.1715245781.git.wqu@suse.com \
    --to=wqu@suse.com \
    --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;
as well as URLs for NNTP newsgroup(s).