linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Paul B. Henson" <henson@acm.org>
To: 'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] thinpool metadata size
Date: Thu, 13 Mar 2014 19:39:06 -0700	[thread overview]
Message-ID: <0d2301cf3f2e$93e8d970$bbba8c50$@acm.org> (raw)
In-Reply-To: <20140313140158.GB5738@redhat.com>

> From: Mike Snitzer
> Sent: Thursday, March 13, 2014 7:02 AM
>
> So if I were relegated to using upstream kernels, I'd track latest
> stable kernel if I could.

I can, and I guess I will :), it just adds a little extra volatility and
work. Maybe by the time the next long-term stable after 3.12 gets picked
thin provisioning and cache will have settled down enough to go with it.

> I'm not sure if the tool tracks the rate of change.  It may account for
> worst case of _every_ block for the provided number of thin devices
> _not_ being shared.

Interesting, then after I added an extra order of magnitude padding for the
number of snapshots, it's probably quite over allocated. But still, again
2.5G isn't very much in the scale of things.

Thanks.

  reply	other threads:[~2014-03-14  2:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 21:21 [linux-lvm] thinpool metadata size Paul B. Henson
2014-03-12 23:35 ` Mike Snitzer
2014-03-13  1:32   ` Paul B. Henson
2014-03-13 14:01     ` Mike Snitzer
2014-03-14  2:39       ` Paul B. Henson [this message]
2014-03-14  5:52         ` matthew patton
2014-03-13 17:20   ` Mike Snitzer
2014-03-14  2:42     ` Paul B. Henson
2014-03-14  3:35       ` Mike Snitzer

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='0d2301cf3f2e$93e8d970$bbba8c50$@acm.org' \
    --to=henson@acm.org \
    --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).