From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: Zhao Lei <zhaolei@cn.fujitsu.com>
Subject: [PATCH 0/5] btrfs-progs: Introduce --extra-dev option
Date: Fri, 4 Sep 2015 21:24:14 +0800 [thread overview]
Message-ID: <cover.1441357933.git.zhaolei@cn.fujitsu.com> (raw)
Some command in current tools can't support filesystem with multiple
loop device, for example:
# truncate -s 200M ./1.img
# truncate -s 200M ./2.img
# mkfs.btrfs -f ./1.img ./2.img
#
# btrfs rescue chunk-recover -v ./1.img
All Devices:
Device: id = 1, name = ./1.img
...
# btrfs rescue super-recover -v ./1.img
All Devices:
Device: id = 1, name = ./1.img
...
# btrfs rescue zero-log ./1.img
warning devid 2 not found already
Clearing log on ./1.img, previous log_root 0, level 0
...
As a workaround, we can bind all of above image files to loop device,
but to make things simple, this patch introduce --extra-dev option,
to specify non-block-device manually, as:
# btrfs rescue chunk-recover -v --extra-device=./2.img ./1.img
All Devices:
Device: id = 2, name = ./2.img
Device: id = 1, name = ./1.img
...
# btrfs rescue super-recover --extra-dev=./2.img -v ./1.img
All Devices:
Device: id = 2, name = ./2.img
Device: id = 1, name = ./1.img
...
# btrfs rescue zero-log --extra-dev=./2.img ./1.img
Clearing log on ./1.img, previous log_root 0, level 0
We can add multiple extra-dev by:
--extra-dev="1.img,2.img"
or
--extra-dev=1.img --extra-dev=2.img
Zhao Lei (5):
btrfs-progs: Introduce --extra-dev option
btrfs-progs: Support extra-dev for btrfs rescue
btrfs-progs: Avoid using uninitialized optind in cmd_rescue_zero_log
btrfs-progs: add help command to btrfs rescue zero-log
btrfs-progs: update manual for --extra-dev and -h for btrfs rescue
Documentation/btrfs-rescue.asciidoc | 13 ++++++-
cmds-rescue.c | 39 +++++++++++++++++----
utils.c | 70 +++++++++++++++++++++++++++++++++++++
utils.h | 5 +++
4 files changed, 119 insertions(+), 8 deletions(-)
--
1.8.5.1
next reply other threads:[~2015-09-04 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 13:24 Zhao Lei [this message]
2015-09-04 13:24 ` [PATCH 1/5] btrfs-progs: Introduce --extra-dev option Zhao Lei
2015-09-04 13:24 ` [PATCH 2/5] btrfs-progs: Support extra-dev for btrfs rescue Zhao Lei
2015-09-04 13:24 ` [PATCH 3/5] btrfs-progs: Avoid using uninitialized optind in cmd_rescue_zero_log Zhao Lei
2015-09-04 13:24 ` [PATCH 4/5] btrfs-progs: add help command to btrfs rescue zero-log Zhao Lei
2015-09-04 13:24 ` [PATCH 5/5] btrfs-progs: update manual for --extra-dev and -h for btrfs rescue Zhao Lei
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=cover.1441357933.git.zhaolei@cn.fujitsu.com \
--to=zhaolei@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).