Description of problem: the thin pool metadata not be placed on different PVs from the pool data Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.set thin_pool_metadata_require_separate_pvs = 1 in /etc/lvm/lvm.conf 2.create vg with 4 PVs 3.lvcreate -i4 -T -V 100m -l1 -n lv11 tsvg/pool1 Actual results: pool1 and lv11 are created successfully and include the same PV : /dev/loop3 [root@laker T2]# lvs -a -olv_name,pool_lv,devices tsvg lvs LV Pool Devices lvs lv11 pool1 lvs pool1 pool1_tdata(0) lvs [pool1_tdata] /dev/loop0(0),/dev/loop1(0),/dev/loop2(0),/dev/loop3(0) lvs [pool1_tmeta] /dev/loop3(1) Expected results: should throw an error that fail to create the thin pool due to insufficient PVs to place the the pool metadata on different PVs from the pool data Additional info:
When reporting lvm bugs, please run the relevant command with -vvvv and attach the output. So in this particular case, attach the output of: lvcreate -vvvv -i4 -T -V 100m -l1 -n lv11 tsvg/pool1 That will reveal what is going wrong.
I can't reproduce your problem, by the way: Not enough PVs with free space available for parallel allocation. Consider --alloc anywhere if desperate.
Created attachment 583149 [details] lvcreate.log
Created attachment 583150 [details] lvm.conf
(In reply to comment #1) > When reporting lvm bugs, please run the relevant command with -vvvv and attach > the output. > > So in this particular case, attach the output of: > > lvcreate -vvvv -i4 -T -V 100m -l1 -n lv11 tsvg/pool1 > > That will reveal what is going wrong. reproduced it and attached the logs. If i have any misunderstanding for the parameter thin_pool_metadata_require_separate_pvs please let me know.
The setting is in a section called 'allocation' in the lvm.conf file. You need to uncomment two more lines. allocation { }
(BTW The value of that setting was not getting logged in -vvvv - something I fixed upstream yesterday.)
I've opened low-priority bug 820203 to report invalid lvm.conf entries.
(In reply to comment #6) > The setting is in a section called 'allocation' in the lvm.conf file. > You need to uncomment two more lines. > > allocation { > } Thanks. It's my fault. One suggestion, uncomment the the section called 'allocation' even if all its' sub-items are commented. This can help the users to avoid the similar fault. # allocation { #>>>snip>>> #}
(In reply to comment #9) > (In reply to comment #6) > > The setting is in a section called 'allocation' in the lvm.conf file. > > You need to uncomment two more lines. > > > > allocation { > > } > > Thanks. It's my fault. > > One suggestion, uncomment the the section called 'allocation' even if all its' > sub-items are commented. This can help the users to avoid the similar fault. > > # allocation { > #>>>snip>>> > #} This suggestion is for the default lvm.conf