All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH v3 00/12] snapshot-merge target
Date: Thu, 19 Nov 2009 12:45:52 -0500	[thread overview]
Message-ID: <20091119174551.GA5852@redhat.com> (raw)
In-Reply-To: <20091119145338.GF6644@agk-dp.fab.redhat.com>

On Thu, Nov 19 2009 at  9:53am -0500,
Alasdair G Kergon <agk@redhat.com> wrote:

> On Thu, Nov 19, 2009 at 09:02:33AM -0500, Mike Snitzer wrote:
> > DM (and LVM) snapshot merging allows a snapshot (its COW store) to be
> > merged back into the snapshot's origin device.
> > One expected use of snapshot merging is rollback of a root filesystem
> > after system upgrades (e.g.: yum update).
> 
> Has the patch to 'Documentation/device-mapper' been written yet?
> (It won't go upstream until we have that of course.  Same for the
> replicator and any other new dm targets.)

Nope, I'll work on that (and adding comments like Andi suggested).  I'll
include these changes into the v4 snapshot-merge patchset submission
that I'll be getting out today.  The v4 patchset will be based on v9 of
the handover patch that we worked on (which I just emailed to dm-devel).

Mike

  reply	other threads:[~2009-11-19 17:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 16:12 [PATCH v3 00/12] snapshot-merge target Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 01/12] dm exception store: add snapshot-merge specific methods Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 02/12] dm exception store: snapshot-merge usage accounting Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 03/12] dm snapshot: add snapshot-merge target Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 04/12] dm snapshot: merge target should not allocate new exceptions Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 05/12] dm snapshot: do not allow more than one merging snapshot Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 06/12] dm snapshot: the merge procedure Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 07/12] dm snapshot: queue writes to an area that is actively being merged Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 08/12] dm snapshot: do not merge a chunk until active writes to it finish Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 09/12] dm snapshot: make exceptions in other snapshots when merging Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 10/12] dm snapshot: make exceptions if merge is dispatching to origin Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 11/12] dm snapshot: redirect accesses to origin if merging snap invalidated Mike Snitzer
2009-11-17 16:12 ` [PATCH v3 12/12] dm snapshot: merge a linear region of chunks using one large IO Mike Snitzer
2009-11-17 16:20   ` Mike Snitzer
2009-11-17 20:35 ` [PATCH v3 13/12] dm snapshot: avoid __minimum_chunk_size() during merge Mike Snitzer
2009-11-19 11:25 ` [PATCH v3 00/12] snapshot-merge target Andi Kleen
2009-11-19 14:02   ` Mike Snitzer
2009-11-19 14:53     ` Alasdair G Kergon
2009-11-19 17:45       ` Mike Snitzer [this message]
2009-11-19 16:08     ` Andi Kleen

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=20091119174551.GA5852@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=andi@firstfloor.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.