From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] thin pool grows but meta data does not?
Date: Wed, 17 Oct 2012 11:30:31 +0200 [thread overview]
Message-ID: <507E7AB7.7080902@gmail.com> (raw)
In-Reply-To: <6004025.KRaXd7Eq3X@laptop>
Dne 16.10.2012 21:17, ben napsal(a):
> Experimenting with thin pools I noticed that extending a thin pool doesn't
> seem to make the metadata larger. Is that the expected behavior?
Yes - metadata resize is not yet supported (but extend will be available in
hopefully near future).
You may see the %use of metadata via: 'lvs -o+metadata_percent'
For now you have to select in front reasonable big metadata size when you
create thin pool. (i.e. 300MB seems to be pretty good size to start with), max
size is <16GB. (There is some auto-estimation based on given thin pool size -
but if you expect the thin pool will significantly grow later - for now you
have to set big enough metadata size for lvcreate command.
Zdenek
prev parent reply other threads:[~2012-10-17 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 19:17 [linux-lvm] thin pool grows but meta data does not? ben
2012-10-17 9:30 ` Zdenek Kabelac [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=507E7AB7.7080902@gmail.com \
--to=zdenek.kabelac@gmail.com \
--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).