Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1486059

Summary:	RFE: provide reminder for missing dlm\|sanlock manager when lockd is running
Product:	Red Hat Enterprise Linux 7	Reporter:	Corey Marthaler <cmarthal>
Component:	lvm2	Assignee:	LVM and device-mapper development team <lvm-team>
lvm2 sub component:	LVM lock daemon / lvmlockd	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	agk, heinzm, jbrassow, lmiksik, mcsontos, prajnoha, teigland, zkabelac
Version:	7.4	Keywords:	FutureFeature
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	lvm2-2.02.175-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 15:22:16 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 2017-08-28 21:24:34 UTC

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

Comment 3 David Teigland 2017-08-28 21:28:48 UTC

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

Comment 6 Corey Marthaler 2017-10-13 23:19:22 UTC

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

Comment 9 errata-xmlrpc 2018-04-10 15:22:16 UTC

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