All of lore.kernel.org
 help / color / mirror / Atom feed
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 22:57:20 -0400	[thread overview]
Message-ID: <1212548240.29076.215.camel@pc.ilinx> (raw)
In-Reply-To: <87f94c370806031720ybdc557ax303c03fb8f4e56ff@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

On Tue, 2008-06-03 at 20:20 -0400, Greg Freemyer wrote:
> Your making it too complicated.
> 
> Effectively the snapshot immediately becomes the primary volume

How can that be done?  I thought the snapshot was simply a device which
upon creation (i.e. before any writes to the origin) is just a series of
block-by-block pointers to the origin.  As blocks in the origin are
changed, those blocks are copied down to the snapshot are replace the
pointer to itself.

So in the case where the origin has had 50% of it's blocks updated, in
order for the snapshot to become the origin, that 50% which has been
written down in to the snapshot need to be written back up into the
origin (along with any blocks which were changed in the snapshot
directly).  How can the snapshot "immediately" become the primary volume
if that data migration has to happen?

b.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-06-04  2:57 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 [this message]
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=1212548240.29076.215.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.