From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: Add invalid snapshot awareness to snapshot merge support
Date: Mon, 16 Jan 2012 11:38:51 -0500 [thread overview]
Message-ID: <20120116163850.GA28811@redhat.com> (raw)
In-Reply-To: <20120114025639.GA10541@redhat.com>
On Fri, Jan 13 2012 at 9:56pm -0500,
Mike Snitzer <snitzer@redhat.com> wrote:
> Prevent an invalid snapshot from being merged via lvconvert.
> Allow an merging snapshot that was invalidated to be removed (useful for
> a snapshot merge that was deferred until next activation but the
> snapshot was invalidated beforehand).
FYI, this patch resolves red hat BZ 761267
prev parent reply other threads:[~2012-01-16 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 2:56 [PATCH] Add invalid snapshot awareness to snapshot merge support Mike Snitzer
2012-01-16 16:38 ` Mike Snitzer [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=20120116163850.GA28811@redhat.com \
--to=snitzer@redhat.com \
--cc=lvm-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.