On 13/01/20 15:49, Zdenek Kabelac wrote:
Hi
Well the size is 'almost' 16GiB - and when the size of thin-pools
metadata is always maintained by lvm2 - it's OK - the size is
internally 'clamped' correctly - the problem is when you use this size
'externally' - so you make 16GiB regular LV used for thin-repair - and
then you swap-in such LV into thin-pool.
So to make it clear - when you 'lvcreate' thin-pool with 16GiB of
metadata - it will work - but then when you will try to fix such
thin-pool - it will fail. So it's always better to create thin-pool
with -L15.812G then using 16G.
Understood, thank you so much.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx
GPG public key ID: FF5F32A8
_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
