Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685723 - exclusive native vdo with lvmlockd will leave remnant lock and cause vgchange to fail "VG stop failed: LVs must first be deactivated"
Summary: exclusive native vdo with lvmlockd will leave remnant lock and cause vgchange...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: David Teigland
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-05 22:07 UTC by Corey Marthaler
Modified: 2019-03-06 14:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Corey Marthaler 2019-03-05 22:07:02 UTC
Description of problem:
[root@host-083 ~]# pcs status
Cluster name: STSRHTS28976
Stack: corosync
Current DC: host-084 (version 2.0.1-4.el8-0eb7991564) - partition with quorum
Last updated: Tue Mar  5 15:59:08 2019
Last change: Tue Mar  5 15:34:00 2019 by root via cibadmin on host-085

3 nodes configured
9 resources configured

Online: [ host-083 host-084 host-085 ]


[root@host-083 ~]# vgcreate  --shared VG /dev/sdf3 /dev/sdf2 /dev/sdf1 /dev/sdb3 /dev/sdb2 /dev/sdb1 /dev/sda3
  Volume group "VG" successfully created
  VG VG starting dlm lockspace
  Starting locking.  Waiting until locks are ready...

[root@host-084 ~]#  vgchange --lock-start VG
  VG VG starting dlm lockspace
  Starting locking.  Waiting until locks are ready...

[root@host-085 ~]#  vgchange --lock-start VG
  VG VG starting dlm lockspace
  Starting locking.  Waiting until locks are ready...

[root@host-084 ~]# lvcreate --activate ey --yes --type vdo -n vdo1 -L 4G VG
  Logical volume "vdo1" created.
[root@host-084 ~]# lvs -a -o +devices
  LV              VG            Attr       LSize    Pool   Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices        
  vdo1            VG            vwi-a-v--- 1016.00m vpool0        0.00                                    vpool0(0)      
  vpool0          VG            dwi-ao----    4.00g               75.05                                   vpool0_vdata(0)
  [vpool0_vdata]  VG            Dwi-ao----    4.00g                                                       /dev/sdg3(0)   

[root@host-084 ~]# lvchange -an VG
[root@host-084 ~]# lvs -a -o +devices
  LV              VG            Attr       LSize    Pool   Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices        
  vdo1            VG            vwi---v--- 1016.00m vpool0                                                vpool0(0)      
  vpool0          VG            dwi-------    4.00g                                                       vpool0_vdata(0)
  [vpool0_vdata]  VG            Dwi-------    4.00g                                                       /dev/sdg3(0)   


[root@host-084 ~]# lvremove VG
Removing VDO pool "vpool0" will remove 1 dependent volume(s). Proceed? [y/n]: y
  Logical volume "vdo1" successfully removed

[root@host-084 ~]# lvs -a -o +devices
  LV              VG            Attr       LSize   Pool   Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices        
[root@host-084 ~]# dmsetup ls
[root@host-084 ~]# 

[root@host-084 ~]# vgchange --lock-stop VG
  VG VG stop failed: LVs must first be deactivated


[root@host-084 ~]# dlm_tool ls
dlm lockspaces
name          lvm_VG
id            0x0eebdff0
flags         0x00000000 
change        member 3 joined 1 remove 0 failed 0 seq 2,2
members       1 2 3 

name          lvm_global
id            0x12aabd2d
flags         0x00000000 
change        member 3 joined 1 remove 0 failed 0 seq 1,2
members       1 2 3 


[root@host-084 ~]# lvmlockctl -i
VG vg_uuid= lock_type= 
LS  lvm_global
LK VG un ver 0
LK GL un ver 2

VG VG lock_type=dlm TQqIz6-hfGP-G2jg-SARC-c0e5-V0fd-PFrKFl
LS dlm lvm_VG
LK VG un ver 5
LK LV ex OfD74f-tSXQ-Jk6D-oycl-WTJg-gsWo-GYQLSj

### All that lvmdbusd noise actually comes in handy here:
[root@host-084 ~]# grep OfD74f-tSXQ-Jk6D-oycl-WTJg-gsWo-GYQLSj /var/log/messages
Mar  5 15:59:51 host-084 lvmdbusd[3196]: 3196:3196 - LV OfD74f-tSXQ-Jk6D-oycl-WTJg-gsWo-GYQLSj vpool0 with lv_attr dwi-ao----, lv_attr[0] = 'd' is not known
Mar  5 15:59:51 host-084 lvmdbusd[3196]: 3196:3196 - LV OfD74f-tSXQ-Jk6D-oycl-WTJg-gsWo-GYQLSj vpool0 with lv_attr dwi-ao----, lv_attr[0] = 'd' is not known
Mar  5 15:59:52 host-084 lvmdbusd[3196]: 3196:3196 - LV OfD74f-tSXQ-Jk6D-oycl-WTJg-gsWo-GYQLSj vpool0 with lv_attr dwi-ao----, lv_attr[0] = 'd' is not known
Mar  5 15:59:52 host-084 lvmdbusd[3196]: 3196:3196 - LV OfD74f-tSXQ-Jk6D-oycl-WTJg-gsWo-GYQLSj vpool0 with lv_attr dwi-ao----, lv_attr[0] = 'd' is not known
Mar  5 16:00:17 host-084 lvmdbusd[3196]: 3196:3196 - LV OfD74f-tSXQ-Jk6D-oycl-WTJg-gsWo-GYQLSj vpool0 with lv_attr dwi-ao----, lv_attr[0] = 'd' is not known
Mar  5 16:00:17 host-084 lvmdbusd[3196]: 3196:3196 - LV OfD74f-tSXQ-Jk6D-oycl-WTJg-gsWo-GYQLSj vpool0 with lv_attr dwi-------, lv_attr[0] = 'd' is not known



Version-Release number of selected component (if applicable):
kernel-4.18.0-74.el8    BUILT: Wed Feb 27 12:52:17 CST 2019
lvm2-2.03.02-6.el8    BUILT: Fri Feb 22 04:47:54 CST 2019
lvm2-libs-2.03.02-6.el8    BUILT: Fri Feb 22 04:47:54 CST 2019
lvm2-dbusd-2.03.02-6.el8    BUILT: Fri Feb 22 04:50:28 CST 2019
lvm2-lockd-2.03.02-6.el8    BUILT: Fri Feb 22 04:47:54 CST 2019
boom-boot-0.9-7.el8    BUILT: Mon Jan 14 14:00:54 CST 2019
cmirror-2.03.02-6.el8    BUILT: Fri Feb 22 04:47:54 CST 2019
device-mapper-1.02.155-6.el8    BUILT: Fri Feb 22 04:47:54 CST 2019
device-mapper-libs-1.02.155-6.el8    BUILT: Fri Feb 22 04:47:54 CST 2019
device-mapper-event-1.02.155-6.el8    BUILT: Fri Feb 22 04:47:54 CST 2019
device-mapper-event-libs-1.02.155-6.el8    BUILT: Fri Feb 22 04:47:54 CST 2019
device-mapper-persistent-data-0.7.6-1.el8    BUILT: Sun Aug 12 04:21:55 CDT 2018
sanlock-3.6.0-5.el8    BUILT: Thu Dec  6 13:31:26 CST 2018
sanlock-lib-3.6.0-5.el8    BUILT: Thu Dec  6 13:31:26 CST 2018
vdo-6.2.0.293-10.el8    BUILT: Fri Dec 14 18:18:47 CST 2018
kmod-kvdo-6.2.0.293-50.el8    BUILT: Mon Feb 25 16:53:12 CST 2019


How reproducible:
Everytime


Note You need to log in before you can comment on or make changes to this bug.