Linux LVM users
 help / color / mirror / Atom feed
From: "Greg Freemyer" <greg.freemyer@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] ANNOUNCE: an experimental implementation of snapshot merging
Date: Tue, 3 Jun 2008 20:20:19 -0400	[thread overview]
Message-ID: <87f94c370806031720ybdc557ax303c03fb8f4e56ff@mail.gmail.com> (raw)
In-Reply-To: <1212537926.2724.16.camel@behemoth.csg.stercomm.com>

Your making it too complicated.

Effectively the snapshot immediately becomes the primary volume and a
bunch of stuff goes on in the background to sync the true primary and
the other snapshots to it.

After everything is in sync, the snapshot is deleted and the true
primary once again becomes the logical primary.

Greg

On Tue, Jun 3, 2008 at 8:05 PM, Chris Cox <chris_cox@stercomm.com> wrote:
> On Tue, 2008-06-03 at 19:38 -0400, Brian J. Murrell wrote:
>> On Tue, 2008-06-03 at 15:43 -0500, Chris Cox wrote:
>> >
>> > I would think this would be VERY hard to do since both the "origin" and
>> > "snapshot" change (file deletes, etc).
>>
>> I don't think it's as difficult as you are thinking it is.  You are
>> thinking of synchronizing filesystems, at the filesystem level, but
>> merging a snapshot back up into the origin does not deal with files or
>> even filesystems.  It deals with block devices and blocks, and is really
>> nothing more than a coordinated:
>>
>> for each COW_block in snapshot; do
>>     for other_snapshot of origin; do
>>         copy origin[COW_block] to other_snapshot[COW_block]
>>         copy snapshot[COW_block] to origin[COW_block]
>>     done
>> done
>>
>> > Do you have a set of rules you
>> > use for the merge?
>>
>> There is no filesystem level merge.  There are no rules needed.
>
> Ok... I'm still a bit confused (sorry)... I'm going to assume
> a last out wins scenario with regards to meta data conflicts
> ... yes.. I know, I'm having a tough time separating out the
> filesystem element from the block device :)
>
> Thanks for the answer... it does make sense (just makes my
> brain hurt).
>
> _______________________________________________
> 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/
>



-- 
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com

  reply	other threads:[~2008-06-04  0:20 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 [this message]
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

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=87f94c370806031720ybdc557ax303c03fb8f4e56ff@mail.gmail.com \
    --to=greg.freemyer@gmail.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