Re: [NFS] Spurious NFS ESTALE errors w/NFSv3 server, non-v3 client

[Neil Brown]

On Friday September 7, [e-mail] wrote:
> On Fri, Sep 07, 2001 at 09:42:16PM +1000, Neil Brown wrote:
> 
> > NFSv2 has a limit of 2Gigabytes per file.  Are the files that you are
> > reading close to, or exceeding, this size?
> 
> 	Not that large, no.  They're on the order of tens of
> 	megabytes, maybe 150 MBytes max.
> 
> > However, I wouldn't expect an ESTALE for that reason.  Can you run
> > "tcpdump -s 1024", the the response that contains the error, and
> > send the dozon or so lines around that?
> 
> 	See below for the end of the tcpdump log, which concludes with
> 	the ESTALE.  I've got the entire log saved, which is about 1.4
> 	MB gzipped, available as http://bklyn.org/~cae/tcpdump.log.gz
> 
> 	For this test, server was linux 2.4.9 w/nfsv3 enabled, client
> 	was 2.4.7 with no nfsv3.  Filesystem mounted on the client as:
> 
> tela:/shn on /shn/tela type nfs (rw,rsize=8192,wsize=8192,soft,addr=192.168.1.2,addr=192.168.1.2)
> 
> 	Let me know if I can provide any add'l info that might help.

Well.....

It looks like you are reading through some large file, then you write
to some other file, and when you try to read the file file again, it
isn't there for some reason....

Is there any chance that the file that you are reading from is being
renamed or removed while it is being read?
Can you try exporting with "no_subtree_check" and see if that makes a
difference?
Could you 
    echo 2 > /proc/sys/sunrpc/nfsd_debug 

and get it to fail again, and then show me that last hundred lines or
so of the kernel log.

NeilBrown