From: Christoph Hellwig <hch@infradead.org>
To: "Amir G." <amir73il@users.sourceforge.net>
Cc: Mike Snitzer <snitzer@redhat.com>,
Lukas Czerner <lczerner@redhat.com>,
linux-ext4@vger.kernel.org, tytso@mit.edu,
linux-kernel@vger.kernel.org, sandeen@redhat.com
Subject: Re: LVM vs. Ext4 snapshots (was: [PATCH v1 00/30] Ext4 snapshots)
Date: Thu, 9 Jun 2011 06:52:20 -0400 [thread overview]
Message-ID: <20110609105220.GA3300@infradead.org> (raw)
In-Reply-To: <BANLkTimyBGfg4+ovGsiGqpCz345qVmU_7A@mail.gmail.com>
On Wed, Jun 08, 2011 at 09:26:11PM +0300, Amir G. wrote:
> In my old next3.sf.net wiki, which I do update from time to time,
> I listed 4 advantages of Ext4 (then next3) snapshots over LVM:
> * Performance: only small overhead to write performance with snapshots
> * Scalability: no extra overhead per snapshot
> * Maintenance: no need to pre-allocate disk space for snapshots
> * Persistence: snapshots don't vanish when disk is full
>
> As far as I know, the only thing that has changed from dm-snap
> to dm-multisnap is the Scalability.
I don't think you have looked at dm-multisnap at all, have you? It
addresses all your points and many more. Take a look at the code which
is in the multisnap branch of https://github.com/jthornber/linux-2.6/,
there's also some slides on it from Linuxtag at:
https://github.com/jthornber/storage-papers/blob/master/thinp-snapshots-2011/thinp-and-multisnap.otp?raw=true
next prev parent reply other threads:[~2011-06-09 10:52 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 18:26 LVM vs. Ext4 snapshots (was: [PATCH v1 00/30] Ext4 snapshots) Amir G.
2011-06-08 18:26 ` Amir G.
2011-06-08 18:49 ` Sunil Mushran
2011-06-09 2:05 ` Yongqiang Yang
2011-06-09 2:05 ` Yongqiang Yang
2011-06-09 10:52 ` Christoph Hellwig [this message]
2011-06-09 11:44 ` Amir G.
2011-06-09 11:44 ` Amir G.
2011-06-10 7:45 ` Amir G.
2011-06-10 7:45 ` Amir G.
2011-06-10 8:08 ` Amir G.
2011-06-10 8:08 ` Amir G.
2011-06-10 9:01 ` Lukas Czerner
2011-06-10 9:01 ` Lukas Czerner
2011-06-10 10:11 ` Joe Thornber
2011-06-10 10:11 ` Joe Thornber
2011-06-10 10:11 ` Joe Thornber
2011-06-10 14:15 ` Amir G.
2011-06-10 14:15 ` Amir G.
2011-06-10 14:15 ` Amir G.
2011-06-10 15:01 ` Joe Thornber
2011-06-10 15:01 ` Joe Thornber
2011-06-10 15:01 ` Joe Thornber
2011-06-11 4:01 ` Amir G.
2011-06-11 4:01 ` Amir G.
2011-06-11 4:01 ` Amir G.
2011-06-11 7:49 ` Joe Thornber
2011-06-11 7:49 ` Joe Thornber
2011-06-11 7:49 ` Joe Thornber
2011-06-11 8:18 ` Alex Bligh
2011-06-11 8:18 ` Alex Bligh
2011-06-11 9:44 ` Amir G.
2011-06-11 9:44 ` Amir G.
2011-06-11 5:41 ` Amir G.
2011-06-11 5:41 ` Amir G.
2011-06-11 7:35 ` Joe Thornber
2011-06-11 7:35 ` Joe Thornber
2011-06-11 7:35 ` Joe Thornber
2011-06-11 9:58 ` Amir G.
2011-06-11 9:58 ` Amir G.
2011-06-11 9:58 ` Amir G.
2011-06-13 8:50 ` Joe Thornber
2011-06-13 8:50 ` Joe Thornber
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=20110609105220.GA3300@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@users.sourceforge.net \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=snitzer@redhat.com \
--cc=tytso@mit.edu \
/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.