btrfs-progs: tune: fix btrfstune --help for -m -M option
The -m | -M option for 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 text. Reviewed-by: Qu Wenruo <wqu@suse.com> Signed-off-by: Anand Jain <anand.jain@oracle.com> Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
parent
24d8119b98
commit
e6a466d44d
|
@ -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, this is an 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, this is an incompat change "
|
||||
"(more lightweight than -u|-U)"),
|
||||
"",
|
||||
"General:",
|
||||
OPTLINE("-f", "allow dangerous operations, make sure that you are aware of the dangers"),
|
||||
|
|
Loading…
Reference in New Issue