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:
I'm using a 2 nodes ctdb cluster. When ctdb is running on both nodes, all consoles of one node are spammed with "dlm: dev_write no op xxxxx xxxxx" messages and this is logged to /var/log/messages (only on one node at a time, but this can be the first or the second across ctdb restarts). Logs stop when stopping ctdb. My setup should be correct as ping_pong read or read/write tests are successful.
Version-Release number of selected component (if applicable):
6.2
How reproducible:
Every time.
Configure a ctdb cluster with 2 nodes over GFS2 (all latest software via yum upgrade at the time of today) and configure CTDB_RECOVERY_LOCK on the shared storage. If I remove the CTDB_RECOVERY_LOCK option, the messages disappear but it's really required.
Actual results:
Feb 3 19:36:23 gfs-01 kernel: dlm: dev_write no op 40001 102b5
Feb 3 19:36:24 gfs-01 kernel: dlm: dev_write no op 40001 102b5
Feb 3 19:36:25 gfs-01 kernel: dlm: dev_write no op 40001 102b5
Feb 3 19:36:26 gfs-01 kernel: dlm: dev_write no op 40001 102b5
Feb 3 19:36:27 gfs-01 kernel: dlm: dev_write no op 40001 102b5
Feb 3 19:36:28 gfs-01 kernel: dlm: dev_write no op 40001 102b5
Feb 3 19:36:29 gfs-01 kernel: dlm: dev_write no op 40001 102b5
Feb 3 19:36:30 gfs-01 kernel: dlm: dev_write no op 40001 102b5
Feb 3 19:36:31 gfs-01 kernel: dlm: dev_write no op 40001 102b5
....
Expected results:
No message if everything is OK, or a fix if it's not.
Hello,
I have searched and found the bug 731775 you mention before posting.
This bug is marked solved in cluster-3.0.12.1-13.el6
Currently the bug is triggered with thoses packages :
uname -r;rpm -q cman;rpm -q ctdb
2.6.32-220.4.1.el6.x86_64
cman-3.0.12.1-23.el6.x86_64
ctdb-1.0.114.3-3.el6.x86_64
I have some news about this issue. It only appears if you run the cluster in compat mode (<group groupd_compat="1" />). As I do not need compat, I just turned it off and all is fine.