Created attachment 705538 [details]
lvmetad -l all output
Description of problem:
I bumped into that bug during testing thinp snapshots on system where lvmetad is activated by default. When lvmetad is turned off, snapshot removal works as intended
Version-Release number of selected component (if applicable): lvm2-2.02.98-5.fc19.x86_64
kernel-3.9.0-0.rc0.git15.1.fc19.x86_64 (but it doesn't matter. using 3.8 series leads into same result)
How reproducible: Always
Steps to Reproduce:
1. Create a thin pool and a thin volume
2. Create few snapshots on top of thin volume
3. Try to remove them
(reproducing script attached)
Actual results: Snapshots won't be removed
Expected results: Snapshots are removed
Created attachment 705539 [details]
/etc/lvm/archive in time of failure
Created attachment 705540 [details]
'dmsetup -c table' output right after the failure
Created attachment 705541 [details]
Created attachment 705542 [details]
'lvs --all' output right after the failure
Created attachment 705544 [details]
thinp metadata dump
Created attachment 705545 [details]
output from reproducer script: basicaly the only interesting part is the last lvremove -vvvv command
dmesg is silent except this line repeated several times:
[ 6250.288694] device-mapper: thin: Deletion of thin device 8 failed.
This is completely un-reproducible on vanilla 3.7.6. Considering the kernel message you get, it might not be related to lvmetad afterall. See also:
#ioctl/libdm-iface.c:1742 device-mapper: message ioctl on failed: Device or resource busy
it would seem that something (udev?) is holding your thin device open and hence it can't be removed? If you can still reproduce the problem, can you just add a sleep 1 between the creation and deletion loops to see if it goes away?
To me looks like a Rawhide version of Bug 889469: check there are no dangling udev cookies left:
This issue is fixed upstream and is present in F19 too.
New lvm2 release is badly wanted.
To clarify: issue is present in F19.
Thanks Marian! It definitely looks like reincarnation of that bug. I see a dozen of hanging cookies after the failure. Thus, I'll try to sort it out with Peter later
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Here's a scratch build with the patch for the dangling cookies + small fix for autoactivation to not trigger when it should not... Please try if it solves the problem:
lvm2-2.02.98-6.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lvm2-2.02.98-7.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
lvm2-2.02.98-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.