From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041215 Firefox/1.0 Red Hat/1.0-12.EL4 Description of problem: Found at Connectathon: In a nutshell, when a NFS client asks for an exclusive lock and the lock is already held, the client will block (waiting for the lock). When the lock is released, the server will call back to the client, granting the lock. The problem is with the client authenticating that callback. The client tries to use information from the export cache which is clearly wrong since the that cache may or may not exist (being its a server only cache).... The symptoms of this issue (at least with a Sun and SGI server) is a continues loop of grant/grant_reply network messages being sent.... Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Run Connectathon against SGI and Sun 2. 3. Additional info:
Created attachment 113130 [details] Patch 1 of 3 needed to fix lockd callbacks
Created attachment 113131 [details] Patch 2 of 3 needed to fix lockd callbacks
Created attachment 113132 [details] Patch 3 of 3 needed to fix lockd callbacks
This looks like it got fixed in U1, but wasn't tracked. Steve, can you confirm we got all the bits included ?
Yes, it appears this made into U1
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-420.html