All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Hendrik Palic <billgotchy@ki.tng.de>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] calculating size of metadata.
Date: Tue, 24 Apr 2012 17:19:43 +0200	[thread overview]
Message-ID: <4F96C48F.3040300@ki.tng.de> (raw)
In-Reply-To: <20120424095252.15fdcb07@bettercgi.com>

Hi,

On 24.04.2012 16:52, Ray Morris wrote:
> It's good think about this because running out of metadata space is no
> fun.

We had this problem already on an other system. We had to migrate to 
another storage with pain. The new storage has a larger space for the 
metadata for sure. .-)

But I want to understand and not only set this size to an high value. 
Therefore this question here.

> We use 181KB for about 300 LVs, where each snapshot is counted as
> two LVs because of the way it's stored.  That's based on the size of the
> backup. vgs shows 8 MB of metadata used, though:
>
> # vgs --units k -o vg_mda_count,vg_mda_free,vg_mda_size clones
> vgs  #VMda VMdaFree  VMdaSize
> vgs      3  7973.50k 16444.00k

Thank you and Lars for your replies. If I understand you right, I have 
to look to the count of LVs I will have in the future and not only on 
the size of my volumegroup.

Ok.

> In any event, on a 19,950,000 MB partition, even 64 MB of metadata
> would represent 0.0006% of the storage. To think of it another way, 64
> MB costs roughly 0.03 cents, so allocate plenty.

Lars stated in his mail to this list, that one entry for a LV should be 
less than 1kb. So if I calculate 2kb for this entry, I will be safe. I 
checked this here and I can confirm this.

If I have a metadata space of 64MB, I am able to create 32000 different 
LV (without snapshots). Right?

Well, that is enought, even with snapshots,

Anyway ... thank you for my enlightment. .-)

Best regards

Jan

      reply	other threads:[~2012-04-24 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 12:23 [linux-lvm] calculating size of metadata Jan-Hendrik Palic
2012-04-24 12:49 ` Lars Ellenberg
2012-04-24 14:52 ` Ray Morris
2012-04-24 15:19   ` Jan-Hendrik Palic [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=4F96C48F.3040300@ki.tng.de \
    --to=billgotchy@ki.tng.de \
    --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 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.