Hi everybody,
on my Proxmox Server I use a LVM Thin Pool for my VMs.
I just wanted to create a snapshot for one of those vms and got this error:
Cannot create new thin volume, free space in thin pool VG_DATA/LV_VMDATA reached threshold.
At a first glance I was surprised as the ~2TB pool is 49% filled. A short google search showed the cause: the pools metadata is ~97% full as "lvs -a" shows:
Then I tried to extend the metadata but that didn't work:
Correct, VG_DATA is completeley holding the LV_VMDATA ThinPool:
My next try was to reduce the size ov LV_VMDATA. But this fails, too:
And what now? Any hint for extending the pools metadata size? I hope I haven't to delete the pool and re-create it ...
Thx in advance!
T0mcat
on my Proxmox Server I use a LVM Thin Pool for my VMs.
I just wanted to create a snapshot for one of those vms and got this error:
Cannot create new thin volume, free space in thin pool VG_DATA/LV_VMDATA reached threshold.
At a first glance I was surprised as the ~2TB pool is 49% filled. A short google search showed the cause: the pools metadata is ~97% full as "lvs -a" shows:
Code:
# lvs -a VG_DATA
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
LV_VMDATA VG_DATA twi-aotz-- 1,82t 49,00 97,51
[LV_VMDATA_tdata] VG_DATA Twi-ao---- 1,82t
[LV_VMDATA_tmeta] VG_DATA ewi-ao---- 120,00m
lvol0 VG_DATA -wi-a----- 120,00m
[lvol1_pmspare] VG_DATA ewi------- 120,00m
[...]Then I tried to extend the metadata but that didn't work:
Code:
# lvextend --poolmetadatasize +250M VG_DATA/LV_VMDATA
Rounding size to boundary between physical extents: 252,00 MiB.
Insufficient free space: 63 extents needed, but only 0 availableCorrect, VG_DATA is completeley holding the LV_VMDATA ThinPool:
Code:
# vgdisplay VG_DATA
--- Volume group ---
VG Name VG_DATA
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 358
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 19
Open LV 10
Max PV 0
Cur PV 1
Act PV 1
VG Size 1,82 TiB
PE Size 4,00 MiB
Total PE 476899
Alloc PE / Size 476899 / 1,82 TiB
Free PE / Size 0 / 0
VG UUID v34GA2-BHGi-9dtO-mFJE-IzhT-Exn4-fTiwwI
# lvdisplay VG_DATA/LV_VMDATA
--- Logical volume ---
LV Name LV_VMDATA
VG Name VG_DATA
LV UUID 0X9xs0-KljV-WCh8-K0k7-y85v-39zt-2brtA7
LV Write Access read/write
LV Creation host, time virtix, 2017-11-22 23:49:22 +0100
LV Pool metadata LV_VMDATA_tmeta
LV Pool data LV_VMDATA_tdata
LV Status available
# open 16
LV Size 1,82 TiB
Allocated pool data 49,00%
Allocated metadata 97,51%
Current LE 476809
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5My next try was to reduce the size ov LV_VMDATA. But this fails, too:
Code:
# lvreduce -L-500M VG_DATA/LV_VMDATA
Thin pool volumes VG_DATA/LV_VMDATA_tdata cannot be reduced in size yet.And what now? Any hint for extending the pools metadata size? I hope I haven't to delete the pool and re-create it ...
Thx in advance!
T0mcat
