From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Gionatan Danti <g.danti@assyoma.it>
Subject: Re: [linux-lvm] Thin metadata volume bigger than 16GB ?
Date: Fri, 22 Jun 2018 22:13:34 +0200 [thread overview]
Message-ID: <b6977938-ecdb-46d8-9c45-8ac048f713b1@redhat.com> (raw)
In-Reply-To: <f158d4decb9c99fec72c600553ef519b@assyoma.it>
Dne 22.6.2018 v 20:10 Gionatan Danti napsal(a):
> Hi list,
> I wonder if a method exists to have a >16 GB thin metadata volume.
>
> When using a 64 KB chunksize, a maximum of ~16 TB can be addressed in a single
> thin pool. The obvious solution is to increase the chunk size, as 128 KB
> chunks are good for over 30 TB, and so on. However, increasing chunksize is
> detrimental for efficiency/performance when heavily using snapshot.
>
> Another simple and very effective solution is to have multiple thin pools, ie:
> 2x 16 GB metadata volumes with 64 KB chunksize is good, again, for over 30 TB
> thin pool space.
>
> That said, the naive but straightforward would be to increase maximum thin
> pool size. So I have some questions:
>
> - is the 16 GB limit an hard one?
Addressing is internally limited to use lower amount of bits.
> - there are practical consideration to avoid that (eg: slow thin_check for
> very bug metadata volumes)?
Usage of memory resources, efficiency.
> - if so, why I can not find any similar limit (in the docs) for cache metadata
> volumes?
ATM we do not recommend to use cache with more then 1.000.000 chunks for
better efficiency reasons although on bigger machines bigger amount of chunks
are still quite usable especially now with cache metadata format 2.
> - what is the right thing to do when a 16 GB metadata volume fill-up, if it
> can not be expanded?
ATM drop data you don't need (fstrim filesystem).
So far there were not many request to support bigger size although there are
plans to improve thin-pool metadata format for next version.
Regards
Zdenek
next prev parent reply other threads:[~2018-06-22 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 18:10 [linux-lvm] Thin metadata volume bigger than 16GB ? Gionatan Danti
2018-06-22 20:13 ` Zdenek Kabelac [this message]
2018-06-23 10:14 ` Gionatan Danti
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=b6977938-ecdb-46d8-9c45-8ac048f713b1@redhat.com \
--to=zkabelac@redhat.com \
--cc=g.danti@assyoma.it \
--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).