All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH] xfs_io: add missed inode command into man page
Date: Fri, 21 Apr 2017 01:06:57 +0800	[thread overview]
Message-ID: <1492708017-14163-1-git-send-email-zlang@redhat.com> (raw)

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>
---
 man/man8/xfs_io.8 | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/man/man8/xfs_io.8 b/man/man8/xfs_io.8
index 19e1ae4..ceb6cf4 100644
--- a/man/man8/xfs_io.8
+++ b/man/man8/xfs_io.8
@@ -650,6 +650,23 @@ sec uses UNIX timestamp notation and is the seconds elapsed since
 nsec is the nanoseconds since the sec. This value needs to be in
 the range 0-999999999 with UTIME_NOW and UTIME_OMIT being exceptions.
 Each (sec, nsec) pair constitutes a single timestamp value.
+.RE
+.PD
+.TP
+.BI " inode [ [ -n ] " number " ] [ -v ]"
+The inode command querys physical information about an inode, it
+returns 1 if any inode number greater than 32 bits exists in the
+filesystem, or 0 if none exist by default. The
+.I number
+is used to specify an inode number, then inode command returns this
+inode number if it's in use, or 0 if not. But if use
+.B \-n
+with
+.I number
+, the next used inode number after this number will be returned, or 0
+if can't find the next one.
+.B \-v
+for verbose mode, the inode number's size in bits will be displayed.
 
 .SH MEMORY MAPPED I/O COMMANDS
 .TP
-- 
2.7.4


             reply	other threads:[~2017-04-20 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 17:06 Zorro Lang [this message]
2017-04-20 17:23 ` [PATCH] xfs_io: add missed inode command into man page Darrick J. Wong
2017-04-20 17:45   ` Eric Sandeen
2017-04-20 17:48     ` 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=1492708017-14163-1-git-send-email-zlang@redhat.com \
    --to=zlang@redhat.com \
    --cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.