Trond Myklebust wrote:
quoted text
> On Wed, 2008-03-12 at 10:55 -0700, Adam Schrotenboer wrote:
>  =20
>> Another excerpt from last night.
>>
>> Mar 12 00:53:16 wanda kernel: nfs: server 192.168.1.27 not responding,=
=20
quoted text
>> 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 =

quoted text
>> changed, 0040755 to 0100644
>>    =20
>
> 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=

quoted text
> 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?
>
>  =20
Quite. OpenSuSE 10.2 stock unmodified kernel.

dolphin:~ # uname -a
Linux dolphin 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006=20
x86_64 x86_64 x86_64 GNU/Linux

dolphin:~ # top -bn1 |grep nfsd


  PID  PPID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAN=
D
 3916     1 root      15   0     0    0    0 S    0  0.0   3:04.42 nfsd
 3942     1 root      15   0     0    0    0 S    0  0.0   3:11.88 nfsd
(there's quite a bit more of these threads than this (32), but they all=20
look the same in top or ps)