All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH v2] dm snapshot: revise snapshot_resume's exception handover
Date: Wed, 4 Nov 2009 17:20:52 -0500	[thread overview]
Message-ID: <20091104222052.GA21348@redhat.com> (raw)
In-Reply-To: <20091104221148.GA19580@redhat.com>

On Wed, Nov 04 2009 at  5:11pm -0500,
Mike Snitzer <snitzer@redhat.com> wrote:

> Until now snapshot_resume only allowed the resuming snapshot to get the
> exception store from another snapshot.
> 
> Revise snapshot_resume's exception handover to allow a snapshot to
> handover its exceptions to another snapshot prior to resuming.
> 
> This is needed to accomodate the following sequence:
> new_snapshot->ctr
> old_snapshot->suspend
> old_snapshot->resume
> new_snapshot->resume
> 
> lvm2 relies on this sequence if 'lvchange --refresh' is used to start a
> snapshot merge that was deferred until both origin and snapshot were not
> in use.

FYI, the above is the last of 3 patches in the "exception handover"
series, the patch order is:

dm snapshot: initial support for exception handover
http://patchwork.kernel.org/patch/55022/

dm snapshot: exception handover improvements
http://patchwork.kernel.org/patch/55569/

dm snapshot: revise snapshot_resume's exception handover
http://patchwork.kernel.org/patch/57787/

  reply	other threads:[~2009-11-04 22:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 21:45 [PATCH] dm snapshot: revise snapshot_resume's exception handover Mike Snitzer
2009-11-04 22:11 ` [PATCH v2] " Mike Snitzer
2009-11-04 22:20   ` Mike Snitzer [this message]
2009-11-04 22:28     ` Mike Snitzer
2009-11-05  1:44       ` Alasdair G Kergon
2009-11-05 13:13         ` Mike Snitzer
2009-11-05 14:14         ` Mike Snitzer

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=20091104222052.GA21348@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@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 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.