I was wondering how I can extend Metadata size in a lvm thin provisioning (on latest Kernel / LVM2).
[root@srv ~]# lvs -a LV VG Attr LSize Pool Origin Data% Meta% lv1 volgroup1 twi-aotz-- 125.00g 25.80 23.32 [lv1_tdata] volgroup1 Twi-ao---- 125.00g [lv1_tmeta] volgroup1 ewi-ao---- 96.00m lvol0 volgroup1 -wi-a----- 96.00m [lvol1_pmspare] volgroup1 ewi------- 96.00m
I have few questions:
- In above 'lvs' command 23.32% is Meta%, this means 23.32% of 96M is used for META (or of total 125G) ?
- lvol1_pmspare is a spare copy of meta. Should i need to extend lvol1_pmspare separately to extend lv1_tmeta.
- Any performance impact by changing thin_pool_chunk_size or setting poolmetadatasize to higher value.
- How to identify ideal metadata size.
Can someone please share your insight and help me on how to extend metadata size.