linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [PATCH] Btrfs-progs: add manpage of btrfs-image -m option
Date: Thu,  8 Aug 2013 10:33:09 +0800	[thread overview]
Message-ID: <1375929189-1920-1-git-send-email-bo.li.liu@oracle.com> (raw)

There is a lack of manpage of btrfs-image '-m' option.

Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
---
 btrfs-image.c        |    1 +
 man/btrfs-image.8.in |    4 ++++
 2 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/btrfs-image.c b/btrfs-image.c
index 82aa4f3..862f081 100644
--- a/btrfs-image.c
+++ b/btrfs-image.c
@@ -2422,6 +2422,7 @@ static void print_usage(void)
 	fprintf(stderr, "\t-o      \tdon't mess with the chunk tree when restoring\n");
 	fprintf(stderr, "\t-s      \tsanitize file names, use once to just use garbage, use twice if you want crc collisions\n");
 	fprintf(stderr, "\t-w      \twalk all trees instead of using extent tree, do this if your extent tree is broken\n");
+	fprintf(stderr, "\t-m      \trestore metadump image onto multiple disks\n");
 	exit(1);
 }
 
diff --git a/man/btrfs-image.8.in b/man/btrfs-image.8.in
index d5ba594..d0fdfc7 100644
--- a/man/btrfs-image.8.in
+++ b/man/btrfs-image.8.in
@@ -42,6 +42,10 @@ problems with your file system tree and need to have it mostly working.
 Walk all the trees manually and copy any blocks that are referenced. Use this
 option if your extent tree is corrupted to make sure that all of the metadata is
 captured.
+.TP
+\fB\-m\fP
+restore metadump image onto multiple disks. Use this option if your metadump
+image is created on a multiple disk made btrfs filesystem.
 .SH AVAILABILITY
 .B btrfs-image
 is part of btrfs-progs. Btrfs is currently under heavy development,
-- 
1.7.7


                 reply	other threads:[~2013-08-08  2:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1375929189-1920-1-git-send-email-bo.li.liu@oracle.com \
    --to=bo.li.liu@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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 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).