From: Goffredo Baroncelli <kreijack@inwind.it>
To: linux-btrfs@vger.kernel.org
Cc: Stefan Behrens <sbehrens@giantdisaster.de>,
Goffredo Baroncelli <kreijack@inwind.it>
Subject: [PATCH 3/3] Add btrfs filesystem info man page.
Date: Fri, 8 Jun 2012 21:12:46 +0200 [thread overview]
Message-ID: <1339182766-15292-4-git-send-email-kreijack@inwind.it> (raw)
In-Reply-To: <1339182766-15292-1-git-send-email-kreijack@inwind.it>
Update the man page to document the "btrfs filesystem info <path>"
command.
---
man/btrfs.8.in | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/man/btrfs.8.in b/man/btrfs.8.in
index be478e0..6d96bf7 100644
--- a/man/btrfs.8.in
+++ b/man/btrfs.8.in
@@ -25,6 +25,8 @@ btrfs \- control a btrfs filesystem
.PP
\fBbtrfs\fP \fBfilesystem defrag\fP\fI [options] <file>|<dir> [<file>|<dir>...]\fP
.PP
+\fBbtrfs\fP \fBfilesystem info\fP\fI <path>\fP
+.PP
\fBbtrfs\fP \fBsubvolume find-new\fP\fI <subvolume> <last_gen>\fP
.PP
\fBbtrfs\fP \fBfilesystem balance\fP\fI <path> \fP
@@ -154,6 +156,12 @@ The start position and the number of bytes to deframention can be specified by \
NOTE: defragmenting with kernels up to 2.6.37 will unlink COW-ed copies of data, don't
use it if you use snapshots, have de-duplicated your data or made copies with
\fBcp --reflink\fP.
+.TP
+
+\fBfilesystem info\fP \fI<path>\fR
+Get filesystem info.
+.TP
+
\fBsubvolume find-new\fR\fI <subvolume> <last_gen>\fR
List the recently modified files in a subvolume, after \fI<last_gen>\fR ID.
.TP
--
1.7.10
next prev parent reply other threads:[~2012-06-08 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 19:12 [RFC][btrfs-progs] add command btrfs filesystem info Goffredo Baroncelli
2012-06-08 19:12 ` [PATCH 1/3] Btrfs-progs: make two utility functions globally available Goffredo Baroncelli
2012-06-08 19:12 ` [PATCH 2/3] Add btrfs filesystem info command Goffredo Baroncelli
2012-06-08 19:12 ` Goffredo Baroncelli [this message]
2012-06-08 19:21 ` [PATCH 3/3] Add btrfs filesystem info man page Jérôme Poulin
2012-06-09 5:36 ` Goffredo Baroncelli
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=1339182766-15292-4-git-send-email-kreijack@inwind.it \
--to=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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).