Linux LVM users
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] ANNOUNCE: an experimental implementation of snapshot merging
Date: Wed, 4 Jun 2008 06:56:16 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806040651320.2902@engineering.redhat.com> (raw)
In-Reply-To: <1212525819.19122.16.camel@behemoth.csg.stercomm.com>

On Tue, 3 Jun 2008, Chris Cox wrote:

> On Tue, 2008-06-03 at 15:26 -0400, 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.
>
> I would think this would be VERY hard to do since both the "origin" and
> "snapshot" change (file deletes, etc).  Do you have a set of rules you
> use for the merge?

The rule is: "origin must not be mounted when you start merging". 
Currently it is not enforced by the lvm tool (you damage your filesystem, 
if you merge over a mounted filesystem), in final version, there will be a 
test to refuse merging in this case.

If you merge a snapshot, you are going to lose the data in the origin. If 
you don't want to lose them, create another snapshot before you start 
merging (then, the new snapshot will contain the data in the origin).

Another rule is: while merging is in progress, don't create other 
snapshots --- well, you can, but they will contain inconsistent midstate. 
Snapshots that were created before the merging started will be preserved 
OK.

Mikulas

  parent reply	other threads:[~2008-06-04 10:56 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 [this message]
2008-06-04 14:01 ` Steeve McCauley
2008-06-05 15:01   ` Mikulas Patocka

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.0806040651320.2902@engineering.redhat.com \
    --to=mpatocka@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