From: Miao Xie <miaox@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>, Josef Bacik <josef@redhat.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: About btrfs chunk tree backups
Date: Thu, 03 Mar 2011 17:01:00 +0800 [thread overview]
Message-ID: <4D6F58CC.9030003@cn.fujitsu.com> (raw)
Hi, Chris and Josef
Recently, I am interested in chunk tree backups, which is described in
Project ideas web. But I found it is hard to be implemented.
The description said "make the mappings discoverable via a block device
scan so that we can recover from corrupted chunk trees", I think it is
hard to find the boundary of each stripe, which is the constituent of
the chunks, via a block device scan according to the current on-disk data
structures. And besides that, even though we find the stripes of each
chunks, we still don't know the order of the stripes in one chunk. So
I think chunk tree backups is hard to be implemented.
Maybe I made some mistakes in understanding this project idea?
Thanks
Miao
next reply other threads:[~2011-03-03 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 9:01 Miao Xie [this message]
2011-03-03 12:37 ` About btrfs chunk tree backups Josef Bacik
2011-03-08 4:14 ` Miao Xie
2011-03-08 15:09 ` 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=4D6F58CC.9030003@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=chris.mason@oracle.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;
as well as URLs for NNTP newsgroup(s).