Bug 1621491

Summary: sanlock 'vgremove --force' doesn't properly clean up lvmlock device with lockspace started
Product: Red Hat Enterprise Linux 7 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: David Teigland <teigland>
lvm2 sub component: LVM lock daemon / lvmlockd QA Contact: cluster-qe <cluster-qe>
Status: CLOSED WONTFIX Docs Contact:
Severity: medium    
Priority: unspecified CC: agk, heinzm, jbrassow, prajnoha, teigland, zkabelac
Version: 7.6   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-15 07:41:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2018-08-23 16:14:38 UTC 
Description of problem:
This is the vgremove issue remaining from bug 1610455.


[root@harding-03 tmp]# pvscan
  Skipping global lock: lockspace not found or started
  Reading VG global without a lock.
  PV /dev/mapper/mpatha1   VG global            lvm2 [249.96 GiB / 249.71 GiB free]
  PV /dev/mapper/mpathd1                        lvm2 [<250.00 GiB]
  PV /dev/mapper/mpathc1                        lvm2 [<250.00 GiB]
  PV /dev/mapper/mpathe1                        lvm2 [<250.00 GiB]
  PV /dev/mapper/mpathb1                        lvm2 [<250.00 GiB]
  Total: 8 [1.49 TiB] / in use: 4 [528.43 GiB] / in no VG: 4 [<1000.00 GiB]

[root@harding-03 tmp]# vgchange --lock-start global
  Skipping global lock: lockspace not found or started
  VG global starting sanlock lockspace
  Starting locking.  Waiting for sanlock may take 20 sec to 3 min...

[root@harding-03 tmp]# vgremove -f global
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  device-mapper: remove ioctl on  (253:19) failed: Device or resource busy
  Unable to deactivate global-lvmlock (253:19).
  Failed to deactivate sanlock lv global/lvmlock
  Volume group "global" successfully removed

[root@harding-03 tmp]# vgs global
  Volume group "global" not found
  Cannot process volume group global

[root@harding-03 tmp]# dmsetup ls | grep lvmlock
global-lvmlock  (253:19)


Version-Release number of selected component (if applicable):

3.10.0-931.el7.x86_64

lvm2-2.02.180-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
lvm2-libs-2.02.180-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
lvm2-cluster-2.02.180-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
lvm2-lockd-2.02.180-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
lvm2-python-boom-0.9-8.el7    BUILT: Tue Aug 21 11:28:32 CDT 2018
cmirror-2.02.180-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
device-mapper-1.02.149-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
device-mapper-libs-1.02.149-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
device-mapper-event-1.02.149-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
device-mapper-event-libs-1.02.149-5.el7    BUILT: Tue Aug 21 11:29:37 CDT 2018
device-mapper-persistent-data-0.7.3-3.el7    BUILT: Tue Nov 14 05:07:18 CST 2017
sanlock-3.6.0-1.el7    BUILT: Tue Dec  5 11:47:21 CST 2017
sanlock-lib-3.6.0-1.el7    BUILT: Tue Dec  5 11:47:21 CST 2017
Comment 4 RHEL Program Management 2021-02-15 07:41:54 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.