Re: mount.nfs: Stale file handle

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 26 May 2021, Scott Andrews wrote:
> 
> cat /proc/fs/nfs/exports
> # Version 1.1
> # Path Client(Flags) # IPs
> / 
> *(ro,no_root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=6b179096:b8b5495a:873908b5:a2b35faa,sec=390003:390004:390005:1)
> /home 
> *(rw,no_root_squash,sync,wdelay,uuid=6b179096:b8b5495a:873908b5:a2b35faa,sec=1)
> 

Apart from the error, this is the only place that anything looks odd.
When / is exported a v4root, there doesn't need to be a uuid=.
It is the same uuid as for /home.
When I experiment I don't get a uuid= for /.

I don't know that this would cause a problem, but maybe it does.

Two extra pieces of debugging info that might be useful:

1/ Get a network trace for port 2049 traffic between client and server
 with tcpdump.
 Be sure to use "-s 0" and provide the binary packet capture - compress
 it and attach it to the email.

2/ Before attempting the mount, and after restarting rpc.mountd on the
server and running "exportfs -f", run "strace -s 1000 -o /tmp/somefile -p ..." on the
rpc.mountd process, then try the mount, then kill strace.
Then provide /tmp/somefile.

NeilBrown


> 
> Can someone help with this issue?
> 
> Thanks for any help/direction you may have
> 
> 




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux