Created attachment 960972 [details] backtrace Description of problem: vgextend receives SIGABRT. When I try to extend a volumegroup. I does say that what I want to do isn't possible, but right after that it crashed. Version-Release number of selected component (if applicable): LVM version: 2.02.98(2) (2012-10-15) Library version: 1.02.77 (2012-10-15) Driver version: 4.27.0 How reproducible: Every time. Steps to Reproduce: 1. I don't really know since I don't know the exact state of the volume group and the partition I was trying to add. 2. 3. Actual results: vgextend said that it can't do that, and subsequently crashed. Expected results: My partition to be added to the volumegroup. Additional info: The partition I was trying to add is formatted with ext4, and it is named dm-0. Maybe it is already part of the volumegroup like lvextend says (it was my swapspace set up by the installer).
Created attachment 960990 [details] -vvvv output of the vgextend command
There were lots and lots of fixes since lvm2 v98 in this area (lvmetad support). We might as well do a rebase for F19.
I've found the exact patch: https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=2f1a571c9707d596d7716cec9488e54ba4c0c946 Will backport that one.
lvm2-2.02.98-16.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/lvm2-2.02.98-16.fc19
Package lvm2-2.02.98-16.fc19: * 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-16.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15832/lvm2-2.02.98-16.fc19 then log in and leave karma (feedback).
lvm2-2.02.98-16.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.