metadata problems while testing lvm2 git with dm_thin_pool

Hello list,

i'm testing dm_thin_pool with lvm2 right now. And i'm always running into the situation that the metadata get's full.

Kernel: 3.5-rc7
lvm/dmeventd: up2date git version 186a2772

I created my thin disk like this:
lvcreate -L 10G -T thinvol/pool1 -V 100G --name disk1

After some autoresizing lvs looks like this:

# lvs
  LV    VG      Attr     LSize   Pool  Origin Data%  Move Log Copy% 
Convert
  disk1 thinvol Vwi-a-tz 100,00g pool1         22,95 

pool1 thinvol twi-a-tz 33,77g 67,97

# dmsetup table
thinvol-pool1: 0 70811648 linear 253:4 0
thinvol-disk1: 0 209715200 thin 253:4 1
thinvol-pool1-tpool: 0 70811648 thin-pool 253:2 253:3 128 0 0
thinvol-pool1_tdata: 0 20971520 linear 8:17 2048
thinvol-pool1_tdata: 20971520 49840128 linear 8:17 20998144
MYVOL-thin_pool2_tdata: 0 20971520 linear 8:129 2048
MYVOL-thin_pool2_tdata: 20971520 31227904 linear 8:129 20998144
thinvol-pool1_tmeta: 0 24576 linear 8:17 20973568
MYVOL-thin_pool2_tmeta: 0 24576 linear 8:129 20973568

Last log messages:
lvm[2786]: Monitoring thin thinvol-pool1-tpool. lvm[2786]: Logical volume pool1 successfully resized lvm[2786]: Thin thinvol-pool1-tpool is now 100% full. lvm[2786]: Extending logical volume pool1 to 33,77 GiB lvm[2786]: Monitoring thin thinvol-pool1-tpool. lvm[2786]: Logical volume pool1 successfully resized lvm[2786]: Thin thinvol-pool1-tpool is now 84% full. lvm[2786]: dm_task_run failed, errno = 22, Invalid argument lvm[2786]: No longer monitoring thin thinvol-pool1-tpool. lvm[2786]: No longer monitoring thin thinvol-pool1-tpool. lvm[2786]: Thin metadata thinvol-pool1-tpool is now 99% full. lvm[2786]: Resize for thinvol/pool1 is not yet supported.

Greets
Stefan

Dne 27.7.2012 13:57, Stefan Priebe - Profihost AG napsal(a):

It's easier to read size of tpool and tmeta device and its fullness with 'lvs -a -o+metadata_percent'

dmsetup status is also use

It looks like you have started with quit small default mda size for thinpool. Then you have slowly increased the size of thin data pool device - but so far there is no support of resize for thin metadata.

So in case you plan to increase heavily the size of data pool - you need to create large metadata device from the beginning.

Size like '--poolmedatasize 400M' should do the trick and should give you pretty decent space to live with. Also the bigger chunk size you will use for provisioning, the smaller the consumption of metadata device will be. (Current default is 64KB - if you could live with i.e. 512KB - you will safe
a lot of metadata space).

Resize of metadata is going to be implemented upstream with newest tools and kernels soon - but so far you have to live with current limits.

Zdenek