1032799 – cpg_dispatch error on gfs2 umount

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 1032799 - cpg_dispatch error on gfs2 umount

Summary: cpg_dispatch error on gfs2 umount

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	dlm
Sub Component:
Version:	7.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	David Teigland
QA Contact:	cluster-qe@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2013-11-20 21:07 UTC by Jaroslav Kortus
Modified:	2021-09-03 12:05 UTC (History)
CC List:	5 users (show)
Fixed In Version:	dlm-4.0.2-6.el7
Doc Type:	Bug Fix
Doc Text:	Previously, after unmounting a gfs2 file system, the dlm_controld service logged the following error message: cpg_dispatch error 9 The message was not related to any negative events, and was thus unnecessary. With this update, dlm_controld no longer logs the message in the described situation.
Clone Of:
Environment:
Last Closed:	2015-11-19 12:44:17 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:2412	0	normal	SHIPPED_LIVE	dlm bug fix update	2015-11-19 11:10:49 UTC

Description Jaroslav Kortus 2013-11-20 21:07:29 UTC

Description of problem:
This message is being printed on every gfs2 umount:
Nov 20 14:56:20 host-061 dlm_controld[12599]: 1965 cpg_dispatch error 9


Version-Release number of selected component (if applicable):
dlm-4.0.2-2.el7.x86_64
kernel-3.10.0-52.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. mount gfs2
2. umount gfs2
3. observe the message in syslog

Actual results:
Nov 20 14:56:20 host-061 dlm_controld[12599]: 1965 cpg_dispatch error 9

Expected results:
no error 

Additional info:
there does not seem to be any negative effect of the error, it's just scaring me in the logs :)

Comment 2 David Teigland 2013-11-20 21:37:24 UTC

This is the method I've always used to leave a cpg:

1. cpg_leave()
2. cpg_dispatch(ALL)
3. within the final confchg callback, call cpg_finalize()

cpg_dispatch is now returning an error for this usage.
If that's what corosync intends to do now, then I'll remove the error message.

Comment 3 David Teigland 2013-12-12 18:02:50 UTC

Is error 9 now intentionally returned in the example above?

Comment 4 Christine Caulfield 2014-03-07 15:56:09 UTC

Yes, it's a 'normal' return value if cpg_finalize() is called within a callback while cpg_dispatch is active. So it can be safely ignored.

Comment 5 RHEL Program Management 2014-03-22 06:29:42 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 Steve Whitehouse 2014-11-17 11:36:08 UTC

So far as I can tell this looks like it is pretty minor - so moving to 7.2.

Comment 9 David Teigland 2015-04-13 16:04:48 UTC

https://git.fedorahosted.org/cgit/dlm.git/commit/?id=b5b06ccf564cd339b91526c13be1dd86d06c1a93

Comment 11 Nate Straz 2015-08-10 19:23:28 UTC

Before w/ dlm-4.0.2-5.el7.x86_64

[root@host-056 ~]# grep -A2 umount /var/log/messages
Aug 10 13:45:25 host-056 qarshd[18967]: Running cmdline: umount -a -t gfs2
Aug 10 13:45:25 host-056 dlm_controld[15655]: 643 cpg_dispatch error 9
Aug 10 13:45:25 host-056 dlm_controld[15655]: 643 cpg_dispatch error 9

After w/ dlm-4.0.2-6.el7.x86_64

[root@host-026 lib]# grep cpg_dispatch /var/log/messages
[root@host-026 lib]# grep -A2 umount /var/log/messages
Aug 10 13:47:57 host-026 qarshd[14664]: Running cmdline: umount -a -t gfs2
Aug 10 13:50:01 host-026 systemd: Started Session 885 of user root.
Aug 10 13:50:01 host-026 systemd: Starting Session 885 of user root.

Comment 12 errata-xmlrpc 2015-11-19 12:44:17 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-2015-2412.html

Note You need to log in before you can comment on or make changes to this bug.