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 1160646

Summary: No way to get PID using dlm_tool lockdebug
Product: Red Hat Enterprise Linux 7 Reporter: Marian Csontos <mcsontos>
Component: dlmAssignee: David Teigland <teigland>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: cluster-maint, djansa, jkortus
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dlm-4.0.6-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 06:35:08 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:
Bug Depends On:    
Bug Blocks: 1295577, 1313485    

Description Marian Csontos 2014-11-05 10:15:23 UTC 
Description of problem:
PID field is not available through `dlm_tool lockdebug` command.

It is accessible:
- using depracated (according to man page) `dlm_tool lockdump`
- or trough `cat /sys/kernel/debug/dlm/${lockspace}_{all,locks}`

Version-Release number of selected component (if applicable):
dlm-4.0.2-4.el7.x86_64
Comment 2 David Teigland 2014-11-05 15:08:19 UTC 
pushed to git
https://git.fedorahosted.org/cgit/dlm.git/commit/?id=34253e1a45d7f1b1bd91de30d32bb13d34cd2464

# ./dlm_tool lockdebug -v test
Resource len  5  "test0"
Master           
Granted
00000001 CR                                    
time 0674106356787638 flags 00000000 00000001 bast 0 0 pid 4061
Comment 5 David Teigland 2016-01-18 23:03:06 UTC 
This change will be included in dlm rebase bz 1295877.
Comment 7 Jaroslav Kortus 2016-09-19 17:13:41 UTC 
After mounting gfs2 fs:
[root@virt-053 tmp]# dlm_tool lockdebug -v gfs2

Resource len 24  "       2            805b"
Master           
Granted
00000011 NL                                    
time 0262307522362445 flags 00000004 00000000 bast 0 0 pid 168264

Resource len 24  "       5           183f2"
Master           
Granted
00000013 PR                                    
time 0262307602500524 flags 00000000 00000000 bast 0 0 pid 170864

Resource len 24  "       2           180e4"
Master           
Granted
0000001a EX                                    
time 0262307603920334 flags 00000000 00000000 bast 0 0 pid 170864


PID field is present, marking as verified with dlm-4.0.6-1.el7.x86_64
Comment 9 errata-xmlrpc 2016-11-04 06:35:08 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://rhn.redhat.com/errata/RHBA-2016-2445.html