linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Josef Bacik <josef@redhat.com>,
	Chris Mason <chris.mason@oracle.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: About btrfs chunk tree backups
Date: Tue, 8 Mar 2011 10:09:37 -0500	[thread overview]
Message-ID: <20110308150936.GA2527@localhost.localdomain> (raw)
In-Reply-To: <4D75AD0D.6070501@cn.fujitsu.com>

On Tue, Mar 08, 2011 at 12:14:05PM +0800, Miao Xie wrote:
> On Thu, 3 Mar 2011 07:37:25 -0500, Josef Bacik wrote:
> > On Thu, Mar 03, 2011 at 05:01:00PM +0800, Miao Xie wrote:
> >> 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?
> >>
> > 
> > We talked about this some earlier this week.  This will require a format change,
> > basically we need to put down some metadata at the start of every chunk so that
> > we can scan the disk and find the chunks.  This could probably be done in a
> > backwards compatible way, we just need to make sure the space for the block
> > thats used is taken up in the extent tree so old kernels don't write over the
> > block.  Thanks,
> 
> Hi, Josef
> 
> Is anyone implementing it now? Maybe we can help him to do some work.
> 

Not that I know of.  Thanks,

Josef

      reply	other threads:[~2011-03-08 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  9:01 About btrfs chunk tree backups Miao Xie
2011-03-03 12:37 ` Josef Bacik
2011-03-08  4:14   ` Miao Xie
2011-03-08 15:09     ` Josef Bacik [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=20110308150936.GA2527@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miaox@cn.fujitsu.com \
    /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).