From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH] btrfs-progs: tune: fix btrfstune --help for -m -M option
Date: Thu, 16 May 2024 12:19:03 +0800 [thread overview]
Message-ID: <4fba8ba903d32bba3f8f92db50823fd7aea38bc4.1715831939.git.anand.jain@oracle.com> (raw)
The -m | -M option for the btrfstune, sounds like metadata_uuid is being
changed which is wrong, the fsid is being changed the original fsid is
being copied into the metadata_uuid. So update the help.
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
tune/main.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/tune/main.c b/tune/main.c
index cfb5b5d6e323..7ae48fe6e80b 100644
--- a/tune/main.c
+++ b/tune/main.c
@@ -113,8 +113,12 @@ static const char * const tune_usage[] = {
"UUID changes:",
OPTLINE("-u", "rewrite fsid, use a random one"),
OPTLINE("-U UUID", "rewrite fsid to UUID"),
- OPTLINE("-m", "change fsid in metadata_uuid to a random UUID incompat change, more lightweight than -u|-U)"),
- OPTLINE("-M UUID", "change fsid in metadata_uuid to UUID"),
+ OPTLINE("-m", "change fsid to a random UUID, copy original fsid into "
+ "metadata_uuid if it's not NULL. Incompat change "
+ "(more lightweight than -u|-U)"),
+ OPTLINE("-M UUID", "change fsid to UUID, copy original fsid into "
+ "metadata_uuid if it's not NULL. Incompat change "
+ "(more lightweight than -u|-U)"),
"",
"General:",
OPTLINE("-f", "allow dangerous operations, make sure that you are aware of the dangers"),
--
2.39.3
next reply other threads:[~2024-05-16 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 4:19 Anand Jain [this message]
2024-05-16 8:28 ` [PATCH] btrfs-progs: tune: fix btrfstune --help for -m -M option Qu Wenruo
2024-05-17 15:37 ` 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=4fba8ba903d32bba3f8f92db50823fd7aea38bc4.1715831939.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).