From: Mike Snitzer <snitzer@redhat.com>
To: Fred van Zwieten <fvzwieten@vxcompany.com>
Cc: "linux-lvm@redhat.com" <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshot limit?
Date: Tue, 24 Jul 2012 10:38:38 -0400 [thread overview]
Message-ID: <20120724143837.GB3772@redhat.com> (raw)
In-Reply-To: <CALVifsY0zh1YA214sMc9tU=ukd1VQWzYVnmnpPgScfNeSiF6Dw@mail.gmail.com>
On Tue, Jul 24 2012 at 10:21am -0400,
Fred van Zwieten <fvzwieten@vxcompany.com> wrote:
> I agree, but that doesn't answer my questions ;-)
please don't top-post.
The old dm-snapshot cannot scale to 150 concurrent read-only
snaps.. sorry.
There would be a 150-way copy out to the 150 different COW areas. Aka,
the dm-snapshot N-way copy-out penalty
thinp snapshots use a single shared pool for the COW area.
prev parent reply other threads:[~2012-07-24 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 8:52 [linux-lvm] Snapshot limit? Fred van Zwieten
2012-07-23 9:00 ` Fred van Zwieten
2012-07-24 13:15 ` Mike Snitzer
2012-07-24 14:21 ` Fred van Zwieten
2012-07-24 14:38 ` Mike Snitzer [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=20120724143837.GB3772@redhat.com \
--to=snitzer@redhat.com \
--cc=fvzwieten@vxcompany.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).