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.
Description of problem:
`dlm_tool ls [-n]` has a hard-coded max of 128 lockspaces. If there are more than 128 lockspaces, then the output is completely empty (except for the header "dlm lockspaces").
1. This max is not documented in the dlm_tool man page or help output.
2. There are no warnings or errors in the output to indicate that there are lockspaces that exist but that are not shown.
3. This max is not configurable.
I presume the max exists to limit the size of replies.
The ideal solution would be to get rid of the max or to make it user-configurable via a command-line option. If this is not possible for some reason, then we should at least document the max in the help output and man page.
Note: If we decide to leave some max value in place (whether as a hard-coded value, or as a user-configurable option with a hard-coded default), then we probably should write something to stderr to inform the user when the number of lockspaces is greater than the max. We might also consider truncating the output in that situation, instead of printing nothing.
-----
Version-Release number of selected component (if applicable):
dlm-4.1.0-1.el8
-----
How reproducible:
Presumably always. I've tried to reproduce the issue by joining 129 lockspaces, but I'm unable to join more than 59. I can't find any hard caps at 60 in the dlm userspace or kernel code, so I don't know what's going on here. I'd appreciate any insight.
[root@fastvm-rhel-8-0-23 pacemaker]# dlm_tool ls | grep -c name
59
[root@fastvm-rhel-8-0-23 pacemaker]# dlm_tool join ls60
Joining lockspace "ls60" permission 600
dlm_new_lockspace ls60 error 16
-----
Steps to Reproduce:
1. Create 129 DLM lockspaces.
2. Run `dlm_tool ls [-n]`
-----
Actual results:
# dlm_tool ls -n
dlm lockspaces
-----
Expected results:
# dlm_tool ls -n
dlm lockspaces
<all lockspaces>
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 (dlm bug fix and enhancement update), 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/RHBA-2023:2288