From: Mike Snitzer <snitzer@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] restoring snapshots
Date: Mon, 20 Sep 2010 09:42:42 -0400 [thread overview]
Message-ID: <20100920134241.GA27548@redhat.com> (raw)
In-Reply-To: <F57F2AD357626644AF76410876025D75529E4F@CGYEX705.encana.com>
On Mon, Sep 20 2010 at 9:15am -0400,
Kinzel, David <David.Kinzel@encana.com> wrote:
> >Is there any plan to add the feature to efficiently
> >restore/apply/commit a snapshot (that is only dump the cow data
> >onto the original volume without writing the whole volume) or
> >does that feature exist already and I missed it?
>
> The newer versions do have the lvmerge feature, and it seems to work in
> RHEL6 beta from what I could see.
Yes, and the changes are also upstream, see:
https://www.redhat.com/archives/linux-lvm/2010-February/msg00029.html
https://www.redhat.com/archives/linux-lvm/2010-May/msg00017.html
Mike
prev parent reply other threads:[~2010-09-20 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 11:16 [linux-lvm] restoring snapshots Stephane Chazelas
2010-09-20 13:15 ` Kinzel, David
2010-09-20 13:42 ` 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=20100920134241.GA27548@redhat.com \
--to=snitzer@redhat.com \
--cc=linux-lvm@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;
as well as URLs for NNTP newsgroup(s).