Hide Forgot
Description of problem: After creating PV on the first thin-LV in the pool, removing the PV fails as the pool itself has PV signature visible and is considered a PV by our tools. This seems to be caused by recent cache removals. Version-Release number of selected component (if applicable): lvm2-2.02.105-0.151.el6.x86_64 - upstream lvm2. How reproducible: 100% Steps to Reproduce: 1. #create a pool vg/pool 2. #create a LV vg/lv in the pool. 3. pvcreate /dev/vg/lv 4. pvremove /dev/vg/lv Actual results: `pvremove /dev/vg/lv` fails with following message: Found duplicate PV 3rYjdZ2W5aTWcI9j1xaQfDK2fIRjC5e0: using /dev/vg/lv not /dev/mapper/vg-pool Found duplicate PV 3rYjdZ2W5aTWcI9j1xaQfDK2fIRjC5e0: using /dev/mapper/vg-pool not /dev/vg/lv Internal error: Physical Volume /dev/vg/lv has a label, but is neither in a VG nor orphan. Expected results: pvremove should pass Additional info:
I reckon that this is something that filters should be taking care of. Thin pools shouldn't be scanned for PV labels.
We are talking here about lvm consuming lvm devices, not some 3rd party. I really do not think user should have to check and modify filters after creating a pool and I am sure it is just my misunderstanding of what you wanted to say.
Problem is solved upstream by these patches: https://www.redhat.com/archives/lvm-devel/2014-March/msg00075.html https://www.redhat.com/archives/lvm-devel/2014-March/msg00076.html https://www.redhat.com/archives/lvm-devel/2014-March/msg00079.html