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:

In our production system running Scientific 6 we experience problems with our nfs mount. Since the update to kernel 2.6.32-220 the dmesg log is filled with errors like 

NFS: directory brand-catcher/sessions contains a readdir loop.  Please contact your server vendor.  Offending cookie: 230704076

This usually happens around one time an hour. We don't notice a real failure - but one time the files of one directory was not accessible anymore and the dmesg was full of those messages.

We have to webservers accessing a common nfs storage on a third server. Webserver1 is printing those errors since the update to the 220 kernel. Webserver2 is still using 2.6.32-131.17.1 and does not show the errors. That makes us quite sure that problem came with the update.

So the problem is likely caused by the client. The nfs server itself is still running 2.6.32-71.29.1 .


Additional info:

There is a report of this problem for centos too:
https://www.centos.org/modules/newbb/viewtopic.php?topic_id=35387

It's stated that this problem was introduced in kernel 2.6.38, fixed in 2.6.39 and may be backported to the recent redhat kernel.

Hi Bjorn,

Please open a support ticket with Red Hat support. They can help diagnose and collect information and inform you of what issues have already been resolved.

Thanks!

This was fixed in the RHEL6.2 update release....