Linux LVM users
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: steeve@terrascale.net,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] ANNOUNCE: an experimental implementation of snapshot merging
Date: Thu, 5 Jun 2008 11:01:15 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806051058200.19487@engineering.redhat.com> (raw)
In-Reply-To: <4846A052.10607@rackable.com>

On Wed, 4 Jun 2008, Steeve McCauley wrote:

> Is this change meant to add cluster support for merging?  I had
> been under the assumption that merging was already a feature of
> snapshots.

My implementation has nothing to do with clustering.

I think there were some userspace programs for off-line merging of 
inactive snapshots. My implementation works in kernel and can be used 
while the snapshot is mounted.

> What is the difference between the current implementation using
> lvremove (which I assumed was where the COW blocks were merged back
> into the original volume) and lvconvert as below?  Why was this
> functionality not kept in lvremove?

lvremove drops the snapshot and forgets its content. lvconvert -M copies 
the snapshot to the origin (I'm now working on to let it automatically 
drop the snapshot when the merging finishes).

Mikulas

> Mikulas Patocka wrote:
>> Hi
>> 
>> Here I release the first experimental implementation of snapshot merging. 
>> Merging allows you to copy data in snapshot back to the origin device. Once 
>> merging starts, it runs on background. When the merging finishes (you see 
>> "0%" with "lvs" command), you should remove the merging snapshot with 
>> lvremove command.
>> 
>> The userspace will still be changed, the kernel is already finished (there 
>> are no known bugs in the kernel, I'm curious about the unknown ones :)
>> 
>> Merging is initiated with "lvconvert -M vg/lv_snapshot" command. When you 
>> initiate merging, make sure that the origin device is not mounted. Snapshot 
>> can be mounted while it's merging is initiated.
>> 
>> During merging, aby reads and writes to the origin device are identical to 
>> accesses to the merging snapshots.
>> 
>> There may be multiple snapshots while one of them is being merged --- 
>> exceptions in other snapshots are being allocated and there snapshots are 
>> kept stable.
>> 
>> Don't try to concurrently merge more than one snapshot (the kernel refuses 
>> to do it, the userspace tools don't know about it --- the userspace will be 
>> rewritten anyway).
>> 
>> The patches are at:
>> http://people.redhat.com/mpatocka/patches/
>> The patches are for 2.6.26-rc4
>> 
>> (besides merging, there are some other bugfixes, I made for the kernel)
>> 
>> Mikulas
>> 
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
> -- 
> Steeve McCauley
> Director of Research and Development
> Rackable Systems
> 407 McGill Street, Suite 1002
> Montreal, Quebec, H2Y 2G3 (Canada)
> Tel: 514-288-3343
> http://www.rackable.com
> :wq
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

      reply	other threads:[~2008-06-05 15:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 19:26 [linux-lvm] ANNOUNCE: an experimental implementation of snapshot merging Mikulas Patocka
2008-06-03 20:32 ` Brian J. Murrell
2008-06-04 11:07   ` Mikulas Patocka
2008-06-04 14:07     ` Brian J. Murrell
2008-06-05 15:09       ` Mikulas Patocka
2008-06-03 20:43 ` Chris Cox
2008-06-03 20:51   ` Stuart D. Gathman
2008-06-03 23:38   ` Brian J. Murrell
2008-06-04  0:05     ` Chris Cox
2008-06-04  0:20       ` Greg Freemyer
2008-06-04  2:57         ` Brian J. Murrell
2008-06-04  3:23           ` Stuart D. Gathman
2008-06-04 11:11           ` Mikulas Patocka
2008-06-04 10:56   ` Mikulas Patocka
2008-06-04 14:01 ` Steeve McCauley
2008-06-05 15:01   ` Mikulas Patocka [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=Pine.LNX.4.64.0806051058200.19487@engineering.redhat.com \
    --to=mpatocka@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=steeve@terrascale.net \
    /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