linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Subject: [PATCH 4/4] btrfs-progs: update manpage for btrfs-image with -m option added
Date: Thu, 19 Jun 2014 09:46:03 +0800	[thread overview]
Message-ID: <1403142363-29482-4-git-send-email-guihc.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <1403142363-29482-1-git-send-email-guihc.fnst@cn.fujitsu.com>

The btrfs-image support multiple devices with -m specified.

Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
---
 Documentation/btrfs-image.txt | 3 +++
 btrfs-image.c                 | 1 +
 2 files changed, 4 insertions(+)

diff --git a/Documentation/btrfs-image.txt b/Documentation/btrfs-image.txt
index 7ee820c..155194a 100644
--- a/Documentation/btrfs-image.txt
+++ b/Documentation/btrfs-image.txt
@@ -48,6 +48,9 @@ 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.
 
+-m::
+Restore for multiple devices, more than 1 device should be provided.
+
 EXIT STATUS
 -----------
 *btrfs-image* will return 0 if no error happened.
diff --git a/btrfs-image.c b/btrfs-image.c
index b235b87..a87dcb7 100644
--- a/btrfs-image.c
+++ b/btrfs-image.c
@@ -2446,6 +2446,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 for multiple devices\n");
 	exit(1);
 }
 
-- 
1.8.1.4


      parent reply	other threads:[~2014-06-19  1:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  1:46 [PATCH 1/4] btrfs-progs: cleanup duplicate assignment of variable leaf for btrfs-image Gui Hecheng
2014-06-19  1:46 ` [PATCH 2/4] btrfs-progs: deal with invalid option combinations " Gui Hecheng
2014-06-23 14:12   ` David Sterba
2014-06-24  1:43     ` Gui Hecheng
2014-06-24  2:36     ` [PATCH v2 " Gui Hecheng
2014-06-24  2:51       ` Gui Hecheng
2014-06-24  3:16     ` [PATCH v3 " Gui Hecheng
2014-06-19  1:46 ` [PATCH 3/4] btrfs-progs: delete invalid output file when btrfs-image failed Gui Hecheng
2014-06-23 14:15   ` David Sterba
2014-06-24  1:41     ` Gui Hecheng
2014-06-24  2:38     ` [PATCH v2 " Gui Hecheng
2014-06-24  3:05       ` Gui Hecheng
2014-06-24  3:16     ` [PATCH v3 " Gui Hecheng
2014-06-24  8:47       ` David Sterba
2014-06-19  1:46 ` Gui Hecheng [this message]

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=1403142363-29482-4-git-send-email-guihc.fnst@cn.fujitsu.com \
    --to=guihc.fnst@cn.fujitsu.com \
    --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).