From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Zorro Lang <zlang@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 1/2] xfs_io: add missed inode command into man page\
Date: Tue, 2 May 2017 16:13:02 -0700 [thread overview]
Message-ID: <20170502231302.GD5973@birch.djwong.org> (raw)
In-Reply-To: <1493010128-8153-1-git-send-email-zlang@redhat.com>
On Mon, Apr 24, 2017 at 01:02:07PM +0800, Zorro Lang wrote:
> There's an "inode" command in xfs_io, it's used to query physical
> information about an inode. But there's not any information about
> it in xfs_io and other related man pages. So document this command
> in the xfs_io man page now.
>
> Signed-off-by: Zorro Lang <zlang@redhat.com>
> ---
>
> Hi,
>
> This V2 follow Eric's suggestion, changed some description, and moved
> the inode command from "FILE I/O" section to "OTHER COMMANDS" section.
>
> Thanks,
> Zorro
>
> man/man8/xfs_io.8 | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/man/man8/xfs_io.8 b/man/man8/xfs_io.8
> index 19e1ae4..a7c2a1e 100644
> --- a/man/man8/xfs_io.8
> +++ b/man/man8/xfs_io.8
> @@ -923,6 +923,30 @@ verbose output will be printed.
> .RE
> .IP
> .B [NOTE: Not currently operational on Linux.]
> +.RE
> +.PD
> +.TP
> +.BI "inode [ [ -n ] " number " ] [ -v ]"
> +The inode command queries physical information about an inode. With
> +no arguments, it will return 1 or 0, indicating whether or not if any
"...whether or not any..."
> +inode numbers greater than 32 bits are currently in use in the filesystem.
> +If given an inode
> +.I number
> +as an argument, then inode command will return this inode
"..as an argument, the command will return the same inode number..."
> +.I number
> +if it's in use, or 0 if not. With
"..if it is in use..."
> +.BI \-n " number"
> +, the next used inode number after this
> +.I number
> +will be returned, or 0 if can't find the next one. With
"...or zero if the supplied inode number is the highest one in use."
> +.B \-v
> +the command will also report the number of bits (32 or 64) used by the
> +inode
> +.I number
> +printed in the result; if no inode
> +.I number
> +was specified on the commandline, the maximum possible inode number in
"..command line..."
> +the system will be printed along with its size.
/me also grumbles about not starting each sentence on a separate line.
Not enough to go fix all the manpages, though. :P
Otherwise,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
(FWIW if Eric wants to massage the patch on the way in rather than
waiting for another send-review cycle that's fine with me.)
--D
> .PD
> .TP
> .BI "set_encpolicy [ \-c " mode " ] [ \-n " mode " ] [ \-f " flags " ] [ \-v " version " ] [ " keydesc " ]
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-02 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 5:02 [PATCH v2 1/2] xfs_io: add missed inode command into man page Zorro Lang
2017-05-02 23:13 ` Darrick J. Wong [this message]
2017-05-02 23:34 ` [PATCH v2 1/2] xfs_io: add missed inode command into man page\ Eric Sandeen
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=20170502231302.GD5973@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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).