From: Eric Sandeen <sandeen@redhat.com>
To: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/3] btrfs-progs: random fixes of btrfs-filesystem documentation
Date: Mon, 11 Aug 2014 10:05:52 -0700 [thread overview]
Message-ID: <53E8F7F0.3060300@redhat.com> (raw)
In-Reply-To: <53E888C3.70807@jp.fujitsu.com>
On 8/11/14, 2:11 AM, Satoru Takeuchi wrote:
> From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
>
> - Simplify and unify the description of both man and usage.
> - Fix to show -m and -d is not exclusive
> with "<path>|<uuid>|<device>|<label>".
> - Add the description about short options for "--mounted" and
> "--all-devices", "-m" and "-d" respectively.
> - Move the descriptions of options to "Options" section.
>
> Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
>
> ---
> Documentation/btrfs-filesystem.txt | 22 ++++++++++++++--------
> cmds-filesystem.c | 15 ++++++++++-----
> 2 files changed, 24 insertions(+), 13 deletions(-)
>
> diff --git a/Documentation/btrfs-filesystem.txt b/Documentation/btrfs-filesystem.txt
> index c9c0b00..fe68496 100644
> --- a/Documentation/btrfs-filesystem.txt
> +++ b/Documentation/btrfs-filesystem.txt
> @@ -20,15 +20,21 @@ SUBCOMMAND
> *df* <path> [<path>...]::
> Show space usage information for a mount point.
>
> -*show* [--mounted|--all-devices|<path>|<uuid>|<device>|<label>]::
> -Show the btrfs filesystem with some additional info.
> +*show* [-d|-m] [<path>|<uuid>|<device>|<label>]::
> +Show the structure of btrfs filesystem(s).
> +
> -If no option nor <path>|<uuid>|<device>|<label> is passed, btrfs shows
> -information of all the btrfs filesystem both mounted and unmounted.
> -If '--mounted' is passed, it would probe btrfs kernel to list mounted btrfs
> -filesystem(s);
> -If '--all-devices' is passed, all the devices under /dev are scanned;
> -otherwise the devices list is extracted from the /proc/partitions file.
> +If none of '<path>|<uuid>|<device>|<label>' is passed, btrfs shows
> +information of all the btrfs filesystems both mounted and unmounted.
that doesn't seem quite correct;
# btrfs filesystem show -m
does not specify '<path>|<uuid>|<device>|<label>' but it only shows
mounted filesystems, not all filesystems.
As I understand it, the -d and -m options control how the command
finds devices; the '<path>|<uuid>|<device>|<label>' argument is
used as a filter for what is found.
> ++
> +The show command finds btrfs filesystems by scanning all the devices
> +in /proc/partitions by default.
I think I would document it something like this:
show [-m|-d] [<path>|<uuid>|<device>|<label>]
Show the structure of btrfs filesystem(s).
By default, the show command scans all devices found in /proc/partitions.
If [-d|--all-devices] is specified, all devices found under /dev are scanned.
If [-m|--mounted] is specified, only mounted (btrfs?) devices are scanned.
By default, the structure of all discovered filesystems is shown.
If any one of [<path>|<uuid>|<device>|<label>] is specified, only filesystems
matching that identifier are shown.
(What seems to be missing, though, is why would the user ever choose to use '-d?')
-Eric
next prev parent reply other threads:[~2014-08-11 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 9:11 [PATCH 1/3] btrfs-progs: random fixes of btrfs-filesystem documentation Satoru Takeuchi
2014-08-11 17:05 ` Eric Sandeen [this message]
2014-08-11 17:14 ` Eric Sandeen
2014-08-11 23:55 ` Satoru Takeuchi
2014-08-11 23:51 ` Satoru Takeuchi
2014-08-12 0:07 ` Eric Sandeen
2014-08-12 7:25 ` [PATCH 1/3 v2] " Satoru Takeuchi
2014-08-12 7:45 ` [PATCH 1/3 v3] " Satoru Takeuchi
2014-08-12 8:06 ` [PATCH 1/3 v4] " Satoru Takeuchi
2014-08-19 15:07 ` David Sterba
2014-08-19 15:10 ` [PATCH 1/3] " David Sterba
2014-08-19 15:33 ` Eric Sandeen
2014-08-20 13:22 ` 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=53E8F7F0.3060300@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.com \
/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).