Bug 785830

Summary: Nfs readdir loop error since kernel 2.6.32-220.*
Product: Red Hat Enterprise Linux 6 Reporter: Björn Ruberg <bjoern>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0CC: baumanmo, jwest, nfs-maint, rwheeler, steved
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-08 18:17:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Björn Ruberg 2012-01-30 18:02:55 UTC 
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.
Comment 2 Ric Wheeler 2012-01-30 21:28:18 UTC 
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!
Comment 4 Steve Dickson 2012-02-08 18:17:55 UTC 
This was fixed in the RHEL6.2 update release....