public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH] xfs_io: document zero and help commands in manpage
Date: Fri, 4 Dec 2015 15:58:08 -0600	[thread overview]
Message-ID: <56620C70.7030707@redhat.com> (raw)

zero & fzero are 2 different commands using 2 different interfaces
to do the same thing, but may as well document them both.

Also explicitly document "help" to be consistent, and to satisfy
the xfstest which checks for all commands being documented.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---


diff --git a/man/man8/xfs_io.8 b/man/man8/xfs_io.8
index 7fd7478..33fbe6a 100644
--- a/man/man8/xfs_io.8
+++ b/man/man8/xfs_io.8
@@ -420,6 +420,13 @@ Call fallocate with FALLOC_FL_ZERO_RANGE flag as described in the
 .BR fallocate (2)
 manual page to allocate and zero blocks within the range.
 .TP
+.BI zero " offset length"
+Call xfsctl with
+.B XFS_IOC_ZERO_RANGE
+as described in the
+.BR xfsctl (3)
+manual page to allocate and zero blocks within the range.
+.TP
 .BI truncate " offset"
 Truncates the current file at the given offset using
 .BR ftruncate (2).
@@ -681,6 +688,9 @@ for the current memory mapping.
 
 .SH OTHER COMMANDS
 .TP
+.BR "help [ " command " ]"
+Display a brief description of one or all commands.
+.TP
 .B print
 Display a list of all open files and memory mapped regions.
 The current file and current mapping are distinguishable from


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2015-12-04 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 21:58 Eric Sandeen [this message]
2015-12-07 14:25 ` [PATCH] xfs_io: document zero and help commands in manpage Brian Foster

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=56620C70.7030707@redhat.com \
    --to=sandeen@redhat.com \
    --cc=xfs@oss.sgi.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