On 12/01/20 19:11, Zdenek Kabelac wrote:
With 16G there is 'problem' (not yet resolved known issue) with
different max size used by thin_repair (15.875G) & lvm2 (15.8125G) tools.
If you want to go with current max size supported by lvm2 - use the
value -L16192M.
Hi Zdenek,
just for confirmation: so using a 16 GiB thin metadata volume *will*
result in activation problems? For example, a
lvcreate --thin system --name thinpool -L 100G --poolmetadatasize 16G
will be affected by the problem you wrote above?
Finally, does it means that lvmthin man page is wrong when stating that
"Thin pool metadata LV sizes can be from 2MiB to 16GiB" (note the GiB
suffix rather than GB)?
Thanks.
--
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/
