From: Zdenek Kabelac <zkabelac@redhat.com>
To: "LVM general discussion and development" <linux-lvm@redhat.com>,
"Tomas Dalebjörk" <tomas.dalebjork@gmail.com>,
"Gionatan Danti" <g.danti@assyoma.it>
Cc: Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] lvm limitations
Date: Thu, 17 Sep 2020 21:17:58 +0200 [thread overview]
Message-ID: <b2dade35-fd56-453e-bee6-1963a324f074@redhat.com> (raw)
In-Reply-To: <E99B2EFD-42A3-4EAA-81C5-E04325569E8D@gmail.com>
Dne 16. 09. 20 v 6:58 Tomas Dalebjörk napsal(a):
> just curious about this:
>
>> Worth to note there is fixed strict limit of the ~16GiB maximum
>> thin-pool kernel metadata size - which surely can be exhausted -
>> mapping holds info about bTree mappings and sharing chunks between
>> devices....
> would that mean that one single thin-pool can maximum hold 16GiB/16 nr of blocks?
thin_metadata_size is the tool that you can play with and see the needed space
of metadata to handle various sized of data volumes.
The bigger the thin-pool chunk is - the less metadata is needed - but the
less 'efficient' snapshot becomes.
> and how about if LVM2 uses VDO as backend, are there more limitations that I need to consider there that are not reflected here
certainly yes - you need to check documentation for VDO how to configure
parameters to held given expected amount of data (with lvm lot of them
is ATM configurable from lvm.conf or profiles)
Zdenek
next prev parent reply other threads:[~2020-09-17 19:17 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
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 [this message]
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=b2dade35-fd56-453e-bee6-1963a324f074@redhat.com \
--to=zkabelac@redhat.com \
--cc=g.danti@assyoma.it \
--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).