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.
DescriptionAlexander Aring
2021-09-30 15:44:26 UTC
Description of problem:
The kernel log buffer gets filled up with a lot of messages like:
[241767.849302] dlm: bin: dlm_callback_resume 25
[241767.854846] dlm: bin: dlm_callback_resume 25
[241767.860373] dlm: bin: dlm_callback_resume 25
...
[241767.865920] dlm: bin: dlm_callback_resume 25
[241767.871352] dlm: bin: dlm_callback_resume 25
[241767.876733] dlm: bin: dlm_callback_resume 25
it is not an error. As DLM recovery stops callback handling by:
dlm_callback_suspend() every callback queue afterwards will be queued in a list until dlm_callback_resume() calls again. It seems lately in connection with GFS2 it becomes more load than usually for unknown reasons.
However we should make it quiet because we can never be sure about how many callbacks was be queued.
Version-Release number of selected component (if applicable):
How reproducible:
I can reproduce it by mount a gfs2 filesystem, run cityscape on all nodes and unmount all filesystems on all nodes at the same time.
However it depends on the load which is involved but it gets quite noisy with that procedure.
Actual results:
A lot of "[241767.871352] dlm: bin: dlm_callback_resume" messages in the kernel log. Which will fill the logs and confuses users.
Expected results:
Less logs with the same amount of information.
Additional info:
There is a patch prepared for upstream to accumulate all amounts of callback queues and print it out only once.
https://listman.redhat.com/archives/cluster-devel/2021-September/msg00107.html
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 (Moderate: kernel security, 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/RHSA-2022:8267