From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfsprogs: document fpunch command in xfs_io
Date: Sat, 08 Dec 2012 13:12:35 -0600 [thread overview]
Message-ID: <50C39123.6050303@sandeen.net> (raw)
Add manpage documentation for the new fpunch command in xfs_io.
Also fix references to the fallocate manpage, which is (now?)
in section 2, not section 3 of the man pages. (Since it's
a syscall, not a library function).
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---
diff --git a/man/man8/xfs_io.8 b/man/man8/xfs_io.8
index f7c6935..9b9ece8 100644
--- a/man/man8/xfs_io.8
+++ b/man/man8/xfs_io.8
@@ -355,17 +355,23 @@ manual page.
.BI "falloc [ \-k ]" " offset length"
Allocates reserved, unwritten space for part of a file using the
fallocate routine as described in the
-.BR fallocate (3)
+.BR fallocate (2)
manual page.
.RS 1.0i
.PD 0
.TP 0.4i
.B \-k
will set the FALLOC_FL_KEEP_SIZE flag as described in
-.BR fallocate (3).
+.BR fallocate (2).
.PD
.RE
.TP
+.BI fpunch " offset length"
+Punches (de-allocates) blocks in the file by calling fallocate with
+the FALLOC_FL_PUNCH_HOLE flag as described in the
+.BR fallocate (2)
+manual page.
+.TP
.BI truncate " offset"
Truncates the current file at the given offset using
.BR ftruncate (2).
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-12-08 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 19:12 Eric Sandeen [this message]
2012-12-08 20:55 ` [PATCH V2] xfsprogs: document all commands in xfs_io Eric Sandeen
2012-12-08 20:58 ` [PATCH] xfstests: ensure all xfs_io commands are documented in the manpage Eric Sandeen
2012-12-08 21:03 ` [PATCH] xfsprogs: remove setfl from xfs_io 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=50C39123.6050303@sandeen.net \
--to=sandeen@sandeen.net \
--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