From: "Yan, Zheng " <yanzheng@21cn.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC] make btrfs-image work
Date: Wed, 20 Jan 2010 10:28:01 +0800 [thread overview]
Message-ID: <3d0408631001191828v65fbb983w482f478b5ed92bbf@mail.gmail.com> (raw)
In-Reply-To: <20100119160417.GA16384@localhost.localdomain>
On Wed, Jan 20, 2010 at 12:04 AM, Josef Bacik <josef@redhat.com> wrote:
> Hello,
>
> btrfs-image would be very helpful for debugging some users problems t=
hat we
> can't reproduce ourselves, but every image that i try and re-create w=
ith
> btrfs-image makes btrfs panic. =A0This is because we zero out the sup=
erblocks
> chunk array and re-create our uuid. =A0This means that we end up not =
being able to
> read the chunk tree on mount, and then even if we could the uuid's of=
the
> metadata we read back wouldn't match the uuid of the device. =A0The w=
ay I've fixed
> this is to just spit the metadata back onto the disk exactly the way =
we got it.
> The caveat to this I think is that if we try to image a multi-device =
setup that
> it won't work right unless we have a multi-device setup to restore th=
e image
> onto. =A0I'm not sure if thats the goal or not. =A0This patch makes t=
he single disk
> case work fine for me. =A0Let me know what you think. =A0Thanks,
>
The goal of btrfs-image is create image that can be examined by btrfsc=
k and
btrfs-debug-tree. btrfs-image creates metadata image for btrfs' logical=
address
space. So your patch only works for the uncommon case that btrfs' logic=
al
address is mapped to offset of device.
Yan, Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-20 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 16:04 [RFC] make btrfs-image work Josef Bacik
2010-01-20 2:28 ` Yan, Zheng [this message]
2010-01-20 2:37 ` Josef Bacik
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=3d0408631001191828v65fbb983w482f478b5ed92bbf@mail.gmail.com \
--to=yanzheng@21cn.com \
--cc=josef@redhat.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