From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 00/10] btrfs-progs: check and tune: add device and noscan options
Date: Wed, 28 Jun 2023 19:56:07 +0800 [thread overview]
Message-ID: <cover.1687943122.git.anand.jain@oracle.com> (raw)
By default, btrfstune and btrfs check scans all and only the block devices
in the system.
To scan regular files without mapping them to a loop device, adds the
--device option.
To indicate not to scan the system for other devices, adds the --noscan
option.
For example:
The command below will scan both regular files and the devices
provided in the --device option, along with the system block devices.
btrfstune -m --device /tdev/td1,/tdev/td2 /tdev/td3
or
btrfs check --device /tdev/td1 --device /tdev/td2 /tdev/td3
In some cases, if you need to avoid the default system scan for the
block device, you can use the --noscan option.
btrfstune -m --noscan --device /tdev/td1,/tdev/td2 /tdev/td3
btrfs check --noscan --device /tdev/td1,/tdev/td2 /tdev/td3
This patch bundle depends on the preparatory patch bundle sent before:
[PATCH 0/6 v3] btrfs-progs: cleanup and preparatory around device scan
And, replaces [1] in the mailing list, as the --device option helper
function is peeled and transformed into a common helper function
in a separate patch.
[1] [PATCH 0/4] btrfs-progs: tune: add --device and --noscan option
Anand Jain (10):
btrfs-progs: common: add --device option helpers
btrfs-progs: tune: consolidate return goto free-out
btrfs-progs: tune: introduce --device option
btrfs-progs: docs: update btrfstune --device option
btrfs-progs: tune: introduce --noscan option
btrfs-progs: docs: update btrfstune --noscan option
btrfs-progs: check: introduce --device option
btrfs-progs: docs: update btrfs check --device option
btrfs-progs: check: introduce --noscan option
btrfs-progs: docs: update btrfs check --noscan option
Documentation/btrfs-check.rst | 6 +++
Documentation/btrfstune.rst | 7 ++++
check/main.c | 45 +++++++++++++++++++++-
common/device-scan.c | 32 ++++++++++++++++
common/device-scan.h | 2 +
tune/main.c | 71 ++++++++++++++++++++++++++++-------
6 files changed, 148 insertions(+), 15 deletions(-)
--
2.31.1
next reply other threads:[~2023-06-28 11:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 11:56 Anand Jain [this message]
2023-06-28 11:56 ` [PATCH 01/10] btrfs-progs: common: add --device option helpers Anand Jain
2023-07-13 18:41 ` David Sterba
2023-07-14 21:28 ` David Sterba
2023-07-18 3:00 ` Anand Jain
2023-06-28 11:56 ` [PATCH 02/10] btrfs-progs: tune: consolidate return goto free-out Anand Jain
2023-06-28 11:56 ` [PATCH 03/10] btrfs-progs: tune: introduce --device option Anand Jain
2023-06-28 11:56 ` [PATCH 04/10] btrfs-progs: docs: update btrfstune " Anand Jain
2023-07-13 18:41 ` David Sterba
2023-07-18 3:07 ` Anand Jain
2023-06-28 11:56 ` [PATCH 05/10] btrfs-progs: tune: introduce --noscan option Anand Jain
2023-06-28 11:56 ` [PATCH 06/10] btrfs-progs: docs: update btrfstune " Anand Jain
2023-06-28 11:56 ` [PATCH 07/10] btrfs-progs: check: introduce --device option Anand Jain
2023-06-28 11:56 ` [PATCH 08/10] btrfs-progs: docs: update btrfs check " Anand Jain
2023-06-28 11:56 ` [PATCH 09/10] btrfs-progs: check: introduce --noscan option Anand Jain
2023-06-28 11:56 ` [PATCH 10/10] btrfs-progs: docs: update btrfs check " Anand Jain
2023-07-13 18:35 ` [PATCH 00/10] btrfs-progs: check and tune: add device and noscan options David Sterba
2023-07-19 7:48 ` Anand Jain
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.1687943122.git.anand.jain@oracle.com \
--to=anand.jain@oracle.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