From: "Dan Kegel" <dank@kegel.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: [linux-lvm] Re: [RFC] Multiple Snapshots - Manageability problem
Date: Wed, 23 Jan 2008 14:36:14 -0800 [thread overview]
Message-ID: <a71bd89a0801231436k3653acfw9bd0a63f027daacf@mail.gmail.com> (raw)
In-Reply-To: <4797686A.4000306@wpkg.org>
On Jan 23, 2008 8:16 AM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
> Vijai Babu Madhavan, Thu, 11 Jan 2007 11:18:13 -0700, wrote:
>
> > The problem of DM snapshots with multiple snapshots have been discussed
> > in the lists quiet a bit (Most recently @
> > https://www.redhat.com/archives/dm-devel/2006-October/msg00034.html).
> >
> > We are currently in the process of building a DM snapshot target that scales
> > well with many snapshots (so that the changed blocks don't get copied to each
> > snapshot). In this process, I would also like to validate an assumption.
>
> Any news on that?
>
> Still, with multiple snapshots write performance degrades linearly - is
> any work done to change that anytime soon?
Yes. Dan Phillips has implemented a shared snapshot exception store.
You can try it out now if you like; it's at http://zumastor.org.
It feels a bit different from the user's point of view than LVM, though.
It plays well with the device mapper and can be used with any
block device (LVM or non-LVM).
- Dan
next prev parent reply other threads:[~2008-01-23 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 16:16 [linux-lvm] Re: [RFC] Multiple Snapshots - Manageability problem Tomasz Chmielewski
2008-01-23 22:36 ` Dan Kegel [this message]
2008-01-24 11:02 ` Tomasz Chmielewski
2008-01-24 13:18 ` Dan Kegel
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=a71bd89a0801231436k3653acfw9bd0a63f027daacf@mail.gmail.com \
--to=dank@kegel.com \
--cc=dm-devel@redhat.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).