From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] ANNOUNCE: an experimental implementation of snapshot merging
Date: Tue, 03 Jun 2008 19:38:06 -0400 [thread overview]
Message-ID: <1212536286.29076.202.camel@pc.ilinx> (raw)
In-Reply-To: <1212525819.19122.16.camel@behemoth.csg.stercomm.com>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
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.
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-06-03 23:38 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 [this message]
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
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=1212536286.29076.202.camel@pc.ilinx \
--to=brian@interlinx.bc.ca \
--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