[linux-lvm] What todo if metadata grows faster than pool data
Oliver Rath
rath at mglug.de
Fri Oct 24 14:08:54 UTC 2014
Hi list,
in my thinpool-volume the used data is now 50% but the used metadata
size is 82%. What happens, if the metadata a running full, bevor data is
full? Do I have to modify metadata size explicitly or does lvm this
automaticly? How can I do this?
At the moment 78 volumes or snaps had been created from this
winthinpool, mostly with size about 100GB.
Tfh,
OIiver
--- Logical volume ---
LV Name winthinpool
VG Name dmivg
LV UUID gDGkhM-jGQq-hSuZ-g4CZ-JtcQ-JcdX-DqD7bi
LV Write Access read/write
LV Creation host, time dmicn20, 2014-10-07 23:54:45 +0200
LV Pool metadata winthinpool_tmeta
LV Pool data winthinpool_tdata
LV Status available
# open 73
LV Size 930,00 GiB
Allocated pool data 50,73%
Allocated metadata 82,61%
Current LE 238080
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:18
More information about the linux-lvm
mailing list