Description of problem: lvm2 command is able to detect a reason why it's refusing device deactivation - i.e. mounted device. However in these days it's more and more common case users are using containers and lvm2 is then not checking mount points from different containers. This leads to confused user who is not able to deactivate LV while plain 'mount' is not showing device is mounted, but in reality it's mounted in different container - systemd and cgmanager is able to easily reach this state. IMHO lvm2 should be able to make a better error state analysis (i.e. look over all /proc/*/mountinfo to check for problematic dm device. Version-Release number of selected component (if applicable): 2.02.114 How reproducible: mount LV in different cgroup. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.