Linux Device Mapper development
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: change tracking with block-level granularity using md
Date: Fri, 20 Dec 2013 16:35:06 +0000	[thread overview]
Message-ID: <20131220163505.GA15982@debian> (raw)
In-Reply-To: <CABhLV00aksW6BzyNswVeytfUQ+q_7PWag1njYs-E=acqqbXoVA@mail.gmail.com>

On Wed, Dec 18, 2013 at 09:04:17AM +0100, Thomas Knauth wrote:
> Hello list,
> 
> I am the author of the following paper
> 
> https://www.usenix.org/conference/lisa13/technical-sessions/papers/knauth

I've been working on a similar problem.  There's a new target called
dm-era taking shape here:

https://github.com/jthornber/linux-2.6/blob/era/drivers/md/dm-era-target.c

It uses bloom filters to track changed blocks.  Userland tools will
access snapshots of the metadata via a metadata snapshot.  I expect to
post the finished code to dm-devel some time in Jan.

More information about what I'm trying to do can be found here:

http://device-mapper.org/blog/2013/11/12/retaining-cache-coherency-with-external-snapshots/


BTW: If you're using dm-thin your backup scenario is trivial.  Just
take a snapshot of the volumes you want to back up.  Take a metadata
snap.  Examine the metadata to see which blocks have changed since you
last backed up.  Copy data.  All you need is already written.

- Joe

      parent reply	other threads:[~2013-12-20 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  8:04 change tracking with block-level granularity using md Thomas Knauth
2013-12-18  8:35 ` Hannes Reinecke
2013-12-20 16:35 ` Joe Thornber [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=20131220163505.GA15982@debian \
    --to=thornber@redhat.com \
    --cc=dm-devel@redhat.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