Re: 2.6.6 breaks kmail (nfs related?)

[Trond Myklebust <trond.myklebust@fys.uio.no>]

På må , 17/05/2004 klokka 07:31, skreiv Andreas Amann:
> fstat64(8, 0xbfffe650)                  = -1 ESTALE (Stale NFS file handle)
> _llseek(8, 0, [373], SEEK_END)          = 0
> write(8, "X\1\0\0", 4)                  = -1 ESTALE (Stale NFS file handle)
> write(8, "\5\0\0\0,\0\0a\0z\0/\0w\0t\0z\0t\0+\0N\0S\0+\0001\0s"..., 344) = -1 
> ESTALE (Stale NFS file handle)

That's wierd... Where could that be coming from? The client is *never*
supposed to generate that on its own. If an ESTALE turns up, it should
always be generated from the server.

Does that same ESTALE show up on a tcpdump/ethereal dump? If so, could
you please check that the filehandle that is contained from the reply to
LOOKUP(".outbox.index") is the same as that which is sent on the
offending GETATTR call?

Cheers,
  Trond