On Thu, Mar 01, 2012 at 08:34:02AM -0700, Orion Poplawski wrote: > On 03/01/2012 06:50 AM, Myklebust, Trond wrote: > >On Wed, 2012-02-29 at 16:21 -0700, Orion Poplawski wrote: > >>On 02/29/2012 04:17 PM, J. Bruce Fields wrote: > >>>On Wed, Feb 29, 2012 at 03:29:36PM -0700, Orion Poplawski wrote: > OMP Reply (Call > >>> > >>>That probably means the server is waiting for the client to return a > >>>delegation. > >>> > >>>Either the server's confused about their being a delegation, or the > >>>client's failing to return one it should? > >>> > > > >As far as I can see from your trace, the client keeps trying to open the > >file '.history', and the server keeps replying with NFS4ERR_DELAY. There > >is nothing in the trace itself that can tell us why the server is > >delaying. > > So, it seems to be on the server side? I didn't get any relief > restarting nfs on the server. Any way to trace what is happening on > the server side? Hm. /proc/locks should be able to tell you whether there's a delegation. (Look for a lock of type LEASE with an inode number matching that of the .history (or whatever file's getting the DELAY return.)) But honestly it's a fairly old kernel. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
