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/2] btrfs-progs: move inode cache removal functionality to "btrfs rescue" group
Date: Mon,  9 Oct 2023 15:16:58 +1030	[thread overview]
Message-ID: <cover.1696826531.git.wqu@suse.com> (raw)

This is the first step to move those cache clearing functionality to
"btrfs rescue", as "btrfs check" doesn't looks that proper just to clear
various cache.

This patchset is handling issue #669 by moving the rarely used inode
cache clearing to "btrfs rescue" as the safe and first step.

Qu Wenruo (2):
  btrfs-progs: move clear-cache.[ch] from check to common directory
  btrfs-progs: move inode cache removal to rescue group

 Documentation/btrfs-check.rst   |  5 +++-
 Documentation/btrfs-rescue.rst  |  6 ++++
 Makefile                        |  6 ++--
 check/main.c                    |  3 +-
 cmds/rescue.c                   | 52 +++++++++++++++++++++++++++++++++
 {check => common}/clear-cache.c |  2 +-
 {check => common}/clear-cache.h |  0
 convert/main.c                  |  2 +-
 tune/main.c                     |  2 +-
 9 files changed, 70 insertions(+), 8 deletions(-)
 rename {check => common}/clear-cache.c (99%)
 rename {check => common}/clear-cache.h (100%)

--
2.42.0


             reply	other threads:[~2023-10-09  4:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  4:46 Qu Wenruo [this message]
2023-10-09  4:46 ` [PATCH 1/2] btrfs-progs: move clear-cache.[ch] from check to common directory Qu Wenruo
2023-10-09  4:47 ` [PATCH 2/2] btrfs-progs: move inode cache removal to rescue group Qu Wenruo
2023-10-09 14:23   ` David Sterba
2023-10-09 20:50     ` Qu Wenruo
2023-10-09 22:47       ` 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.1696826531.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).