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.
How easy is it to reproduce this problem? If I can reproduce it myself I can try to see what kernel version in 6.1 the problem started happening in. If I cant reproduce it maybe I can give someone a series of 6.1 development/interm kernels so we can try to pinpoint a change thats resposible for the regression.
Larry Woodman
You can also refer to bug # 709758 and our support case # 477247 for this issue.
But, basicly when we discovered this, our cluster was just begining to take place, it was as simple as :
- 8 nodes cluster
- Fibre channel attached storage
- Some service (like apache/php, with no trafic) running on top of gfs2, where the FS is mounted on more than one node.
Wait a few hours, and it was enought to see a good spike in cpu, and during the issue, ssh console was not usable at all (i.e. slow as hell to respond).
Larry,
709758 is the corosync part of this bug where we converted mutex to spinlocks. After we did this, the customer still had problems where the system would still be unusable periodically but only with RHEL6.1 kernels. The customer was able to identify the system misbehaved with only a specific kernel (with the updated packages from 709758).
The RHEL process requires separate bugs for different components even if they have the same problem.
Created attachment 521997 [details] sar data