On Wed, 2008-03-12 at 10:55 -0700, Adam Schrotenboer wrote:
> Another excerpt from last night.
>
> Mar 12 00:53:16 wanda kernel: nfs: server 192.168.1.27 not responding,
> still trying
> Mar 12 00:53:18 wanda kernel: nfs: server 192.168.1.27 OK
> Mar 12 00:54:29 wanda kernel: nfs_update_inode: inode 1075049148 mode
> changed, 0040755 to 0100644
Hang on. That does not look like an XID collision problem...
That code path basically means that the fileids/inode numbers match,
which would not be the case if we were talking about an XID collision
causing the reply cache to replay an old request...
That message rather symptomatic of a filehandle reuse problem. In other
words a NFS filehandle appears to be reused to label a regular file
after it has been used for a directory with the same fileid/inode
number. That is a definite server bug.
Are you sure that you are using the regular kernel nfs server?
--
Trond Myklebust
NFS client maintainer
NetApp
[email protected]
http://www.netapp.com