linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] efficiently copying snapshot data.
Date: Sat, 10 Jul 2010 16:50:32 +0100	[thread overview]
Message-ID: <20100710155031.GA26290@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1007092051070.29512@bmsred.bmsi.com>

On Fri, Jul 09, 2010 at 09:01:02PM -0400, Stuart D. Gathman wrote:
> Copy to a regular LV on the target system, and then do some dmsetup 
> and metadata magic to turn the LV (which is a copy of a COW table) into a
> snapshot of the master LV with the COW already populated.

> I don't think such a utility exists.

lvconvert -s  does this, regardless of what the man page might lead you
to believe!

Alasdair

  parent reply	other threads:[~2010-07-10 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 23:47 [linux-lvm] efficiently copying snapshot data Michael Closson
2010-07-10  0:38 ` Ray Morris
2010-07-10  1:01   ` Stuart D. Gathman
2010-07-10  1:14     ` Ray Morris
2010-07-10 15:50     ` Alasdair G Kergon [this message]
2010-07-12 21:25       ` Michael Closson

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=20100710155031.GA26290@agk-dp.fab.redhat.com \
    --to=agk@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).