Description of problem: If you do the following: # vgremove -f fubar & pvs when the vg contains a number of LVs, then the pvs command runs and exits with exit code (5) and warning message: Volume group "fubar" successfully removed WARNING: Volume Group fubar is not consistent. Volume group "fubar" not found Cannot process volume group fubar Version-Release number of selected component (if applicable): Don't believe this is applicable, but this is what I was running LVM version: 2.02.132(2) (2015-09-22) Library version: 1.02.110-git (2015-09-22) Driver version: 4.33.0 How reproducible: Always Steps to Reproduce: [root@localhost tools]# vgs [root@localhost tools]# pvs PV VG Fmt Attr PSize PFree /dev/sdb lvm2 --- 18.00g 18.00g /dev/sdc lvm2 --- 18.00g 18.00g /dev/sdd lvm2 --- 18.00g 18.00g /dev/sde lvm2 --- 18.00g 18.00g [root@localhost tools]# vgcreate fubar /dev/sdd Volume group "fubar" successfully created [root@localhost tools]# lvcreate -L4m fubar Logical volume "lvol0" created. [root@localhost tools]# lvcreate -L4m fubar Logical volume "lvol1" created. [root@localhost tools]# lvcreate -L4m fubar Logical volume "lvol2" created. [root@localhost tools]# lvcreate -L4m fubar Logical volume "lvol3" created. [root@localhost tools]# vgremove -f fubar & pvs || echo $? [2] 20159 Logical volume "lvol0" successfully removed Logical volume "lvol1" successfully removed Logical volume "lvol2" successfully removed Logical volume "lvol3" successfully removed Volume group "fubar" successfully removed WARNING: Volume Group fubar is not consistent. Volume group "fubar" not found Cannot process volume group fubar PV VG Fmt Attr PSize PFree /dev/sdb lvm2 --- 18.00g 18.00g /dev/sdc lvm2 --- 18.00g 18.00g /dev/sde lvm2 --- 18.00g 18.00g 5 Actual results: Exit code of 5 and a warning in stderr with one of the PVs missing Expected results: Exit code of 0 with all the PVs listed Additional info:
Created attachment 1085365 [details] Debug output from both commands using -vvvv
fixed here https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=1a74171ca5682a684d0e05c6090c3d33cab8795b
(In reply to David Teigland from comment #2) > fixed here > https://git.fedorahosted.org/cgit/lvm2.git/commit/ > ?id=1a74171ca5682a684d0e05c6090c3d33cab8795b Fix removes the exit code 5 and the warning, but the PVs associated with the VG are still missing. This is not an acceptable solution.
missing output fixed here https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=6624833839645cbe75af073fd1dd9ab8c78e0d03
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Tested, working as expected.