Red Hat Bugzilla – Bug 1486059
RFE: provide reminder for missing dlm|sanlock manager when lockd is running
Last modified: 2018-04-10 11:23:08 EDT
Description of problem: This is covered in the man page, but in the event that isn't heeded, if dlm or sanlock isn't running but lockd is, provide reminder warning. [root@host-113 ~]# vgchange --lockstart Skipping global lock: lockspace not found or started [root@host-113 ~]# pvcreate /dev/sda1 Global lock failed: check that global lockspace is started Version-Release number of selected component (if applicable): 3.10.0-693.1.1.el7.x86_64 lvm2-2.02.171-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017 lvm2-libs-2.02.171-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017 lvm2-cluster-2.02.171-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017 device-mapper-1.02.140-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017 device-mapper-libs-1.02.140-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017 device-mapper-event-1.02.140-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017 device-mapper-event-libs-1.02.140-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017 device-mapper-persistent-data-0.7.0-0.1.rc6.el7 BUILT: Mon Mar 27 10:15:46 CDT 2017 cmirror-2.02.171-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017 sanlock-lib-3.5.0-1.el7 BUILT: Wed Apr 26 09:37:30 CDT 2017 lvm2-lockd-2.02.171-8.el7 BUILT: Wed Jun 28 13:28:58 CDT 2017
fixed by https://sourceware.org/git/?p=lvm2.git;a=commit;h=f847fcd31a41f61dd81b30ac91f3e2720088b8f2 # pvcreate /dev/sdc Start a lock manager, lvmlockd did not find one running. Global lock failed: check that global lockspace is started # vgchange --lockstart Start a lock manager, lvmlockd did not find one running. Skipping global lock: lockspace not found or started
Fix verified in the latest rpms. lvm2-2.02.175-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017 lvm2-libs-2.02.175-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017 lvm2-cluster-2.02.175-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017 device-mapper-1.02.144-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017 device-mapper-libs-1.02.144-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017 device-mapper-event-1.02.144-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017 device-mapper-event-libs-1.02.144-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017 device-mapper-persistent-data-0.7.0-0.1.rc6.el7 BUILT: Mon Mar 27 17:15:46 CEST 2017 sanlock-lib-3.5.0-1.el7 BUILT: Wed Apr 26 16:37:30 CEST 2017 lvm2-lockd-2.02.175-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017 [root@host-081 ~]# vgremove STSRHTS248021 Start a lock manager, lvmlockd did not find one running. Global lock failed: check that global lockspace is started [root@host-081 ~]# pvs /dev/sda1 Start a lock manager, lvmlockd did not find one running. Skipping global lock: lockspace not found or started Reading VG STSRHTS248021 without a lock. PV VG Fmt Attr PSize PFree /dev/sda1 STSRHTS248021 lvm2 a-- 24.98g 16.98g [root@host-081 ~]# vgchange --lockstart STSRHTS248022 Start a lock manager, lvmlockd did not find one running. Skipping global lock: lockspace not found or started VG STSRHTS248022 start failed: lock manager dlm is not running [root@host-081 ~]# pvcreate /dev/sdd1 Start a lock manager, lvmlockd did not find one running. Global lock failed: check that global lockspace is started
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0853