All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Automatic snapshot system?
Date: Mon Dec  3 08:18:02 2001	[thread overview]
Message-ID: <20011203152024.B10584@sistina.com> (raw)
In-Reply-To: <ufa1yige1hm.fsf@epithumia.math.uh.edu>; from tibbs@math.uh.edu on Fri, Nov 30, 2001 at 09:12:53AM -0600

On Fri, Nov 30, 2001 at 09:12:53AM -0600, Jason L Tibbitts III wrote:
> >>>>> "JT" == Joe Thornber <thornber@btconnect.com> writes:
> 
> JT> It's a nice idea, but with the current implementation there's no
> JT> way I'd want 100 snapshots of the same origin hanging around.
> 
> They wouldn't all be of the same LV, fortunately; I split my VG up
> into lots of manageable chunks.  (Large users get a volume to
> themselves, small users get grouped into various user volumes.)  But
> still, I assume that you have some details of performance with the
> current snapshot implementation.  Is it that bad?

Well, it does

- copy on write (COW) synchronously *before* et allows the write to
  the original LV to proceed

- do multiple reads in case you`ve got multiple snapshots

- does the COWs for multiple snapshots sequentially

This leads to an unecessary read per additional snapshot on the original
LV and therefore to something around n-times delay in case you've got
n snapshots.

We will have an asynchrounous implementation which avoids multiple
reads with LVM2.

> 
>  - J<
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2001-12-03  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29  1:07 [linux-lvm] Automatic snapshot system? Jason L Tibbitts III
2001-11-29  2:46 ` Petro
2001-11-29 14:41   ` Jason L Tibbitts III
2001-11-29 14:58     ` Petro
2001-11-29 15:16       ` Jason L Tibbitts III
2001-11-30  2:53     ` Joe Thornber
2001-11-30  9:11       ` Jason L Tibbitts III
2001-12-03  8:18         ` Heinz J . Mauelshagen [this message]

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=20011203152024.B10584@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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.