linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: "LVM general discussion and development" <linux-lvm@redhat.com>,
	"Tomas Dalebjörk" <tomas.dalebjork@gmail.com>
Subject: Re: [linux-lvm] lvm limitations
Date: Sun, 30 Aug 2020 19:33:06 +0200	[thread overview]
Message-ID: <8f19f639-107d-610d-0083-596d0c21a081@redhat.com> (raw)
In-Reply-To: <83DAD1FF-6CE0-4725-A24D-2AE529433AEE@gmail.com>

Dne 30. 08. 20 v 1:25 Tomas Dalebj�rk napsal(a):
> hi
> 
> I am trying to find out what limitations exists in LVM2
> 
> nr of logical volumes allowed to be created per volume group
> 

Hi

There is no 'strict' maximum in term of we would limit to i.e. 10000LV per VG.

It's rather limitation from overall practical usability and the space you
may need to allocate to store the metadata  (pv/vgcreate --metadatasize)

The bigger the metadata gets with more LVs - the slower the performance of 
processing gets (as there is rather slow code doing all sorts of validation).
You need much bigger metadata areas during 'pv/vgcreate' to be prepared AHEAD
of time (since lvm2 does not support expansion of metadata space).

For illustration  for 12.000 LVs you need ~4MiB just store Ascii metadata 
itself, and you need metadata space for keeping at least 2 of them.

Handling of operations like  'vgremove' with so many LVs requires 
signification amount of your CPU time.

Basically to stay within bounds - unless you have very good reasons
you should probably stay in range of low thousands to keep lvm2 performing
reasonably well.

If there would be some big reason to support 'more' - it's doable - but 
currently it's deep-down on the TODO list ;)

Zdenek

  reply	other threads:[~2020-08-30 17:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29 23:25 [linux-lvm] lvm limitations Tomas Dalebjörk
2020-08-30 17:33 ` Zdenek Kabelac [this message]
2020-08-30 18:01   ` Gionatan Danti
2020-08-30 19:30     ` Zdenek Kabelac
2020-09-01 13:21       ` Gionatan Danti
2020-09-15 19:16         ` Tomas Dalebjörk
2020-09-15 20:08           ` Zdenek Kabelac
2020-09-15 21:24             ` Tomas Dalebjörk
2020-09-15 21:30               ` Stuart D Gathman
2020-09-15 22:24                 ` Gionatan Danti
2020-09-15 21:47               ` Zdenek Kabelac
2020-09-15 22:26                 ` Gionatan Danti
2020-09-16  4:25                   ` Tomas Dalebjörk
2020-09-17 19:24                     ` Zdenek Kabelac
2020-09-16  4:31                   ` Tomas Dalebjörk
2020-09-16  4:58                   ` Tomas Dalebjörk
2020-09-17 19:17                     ` Zdenek Kabelac
2020-09-17 19:32                   ` Zdenek Kabelac
2020-09-14  6:03 Tomas Dalebjörk

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=8f19f639-107d-610d-0083-596d0c21a081@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=tomas.dalebjork@gmail.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).