linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Larry Dickson" <ldickson@cuttedge.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshot question... [scaling problem]
Date: Thu, 24 Apr 2008 10:19:56 -0700	[thread overview]
Message-ID: <1c748a490804241019l30e33fceyfd6b410119f94e15@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0804241151140.30374-100000@bmsred.bmsi.com>

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

>Then you can't delete an older snapsnot until you delete all newer ones.

Not true of what I was proposing - are we talking past each other? If snap 0
is the current (live) COW, and snap -k refers to time(-k) = time(snap 0) -
k*(interval), then reading the virtual
data for time(-k) involves looking at snap -k, then snap -k+1, ... snap 0,
current data; but stopping the first time your block gets a hit. The only
point with a race is {snap 0, current data}. So you can't delete a NEWER
snapshot until you delete all OLDER ones (because the virtual older snaps
need the newer COWs). That seems a small price to pay, since normally you
throw them away oldest first.

Larry

On 4/24/08, Stuart D. Gathman <stuart@bmsi.com> wrote:
>
> On Thu, 24 Apr 2008, Larry Dickson wrote:
>
> > There's an almost trivial variant on this, where you keep the
> > (read-only) snapshots in a time-ordered sequence, and freeze the last
> > snapshot COW at the same moment as you start the next snapshot. Then
> writing
> > only ever hits the new snapshot COW, and reading from any older snapshot
> > (virtual) volume involves figuring out which is the first after that to
> hold
> > the block, but still involves reading only one block. I wonder why LVM
> does
> > not do this. Perhaps Zumastor does? Or somebody else?
>
> Then you can't delete an older snapsnot until you delete all newer ones.
>
> Zumastor works by using one COW table shared between all snapshots
> for a volume.  Blocks are added to the COW in time order.  The origin
> ignores COW blocks before the last time point (block offset), writing a
> new COW
> block for any modified since that time point.  The snapshots also use
> timepoints in a way that is straightforward, but I don't want to think
> about it at the moment :-)
>
> --
>              Stuart D. Gathman <stuart@bmsi.com>
>    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
> "Confutatis maledictis, flammis acribus addictis" - background song for
> a Microsoft sponsored "Where do you want to go from here?" commercial.
>
> _______________________________________________
> 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/
>

[-- Attachment #2: Type: text/html, Size: 3004 bytes --]

  reply	other threads:[~2008-04-24 17:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 10:30 [linux-lvm] Snapshot question Charles Marcus
2008-04-22 10:47 ` Stephane Chazelas
2008-04-22 16:12   ` Brian J. Murrell
2008-04-22 16:38     ` Stephane Chazelas
2008-04-22 16:54       ` Dan Kegel
2008-04-22 17:39         ` Dan Kegel
2008-04-23 11:49           ` Stephane Chazelas
2008-04-22 16:51     ` Dan Kegel
2008-04-24  3:57     ` [linux-lvm] Snapshot question... [scaling problem] Ross Boylan
2008-04-24  4:10       ` Dan Kegel
2008-04-24 14:21         ` Larry Dickson
2008-04-24 15:59           ` Stuart D. Gathman
2008-04-24 17:19             ` Larry Dickson [this message]
2008-04-22 16:28   ` [linux-lvm] Snapshot question Charles Marcus
2008-04-22 16:47     ` dave
2008-04-22 17:09       ` Charles Marcus
2008-04-23 10:08         ` Charles Marcus
2008-04-22 16:52     ` Stephane Chazelas

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=1c748a490804241019l30e33fceyfd6b410119f94e15@mail.gmail.com \
    --to=ldickson@cuttedge.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;
as well as URLs for NNTP newsgroup(s).