Re: [gentoo-user] mount.nfs stale nfs handle [SOLVED]

[Alexander Puchmayr <alexander.puchmayr@linznet.at>]

Am Sonntag, 29. Juni 2014, 21:34:07 schrieb Alexander Puchmayr:
> Hi there,
> 
> After upgrading my server to latest stable release of gentoo, none of my
> clients is able to mount any nfs share from the server anymore.
> 
> Symptoms:
> $ mount -v -t nfs poseidon:/datadisk/ /mnt/gentoo/
> mount.nfs: timeout set for Sun Jun 29 19:33:40 2014
> mount.nfs: trying text-based options
> 'vers=4,addr=192.168.1.6,clientaddr=192.168.1.2'
> mount.nfs: mount(2): Protocol not supported
> mount.nfs: trying text-based options 'addr=192.168.1.6'
> mount.nfs: prog 100003, trying vers=3, prot=6
> mount.nfs: trying 192.168.1.6 prog 100003 vers 3 prot TCP port 2049
> mount.nfs: prog 100005, trying vers=3, prot=17
> mount.nfs: trying 192.168.1.6 prog 100005 vers 3 prot UDP port 60058
> mount.nfs: mount(2): Stale NFS file handle
> mount.nfs: trying text-based options
> 'vers=4,addr=192.168.1.6,clientaddr=192.168.1.2'
> mount.nfs: mount(2): Protocol not supported
> mount.nfs: trying text-based options 'addr=192.168.1.6'
> mount.nfs: prog 100003, trying vers=3, prot=6
> mount.nfs: trying 192.168.1.6 prog 100003 vers 3 prot TCP port 2049
> mount.nfs: prog 100005, trying vers=3, prot=17
> mount.nfs: trying 192.168.1.6 prog 100005 vers 3 prot UDP port 60058
> mount.nfs: mount(2): Stale NFS file handle
> [...]
> mount.nfs: Connection timed out
> $
> 
[...]

The important hint I finally found after searching for hours:
> http://www.mmacleod.ca/blog/2014/02/nfs-exports-and-xfss-inode64-mount-option/
Thanks to the guy who wrote it!

The key is that
* I'm exporting more than one different (sub-)directories on the same filesystem
* For some reason it gets confused with the uuid/fsid; Can't find the page 
where I found that anymore :-(
* the actual device the exported filesystem resides on is /dev/md127 and not 
/dev/md0 as I originally wanted. Since I did not regard the number, I ignored 
this fact, but I also found hints that this might cause the problem of the 
previous point. 

The suggested solution was to add a *unique* fsid=xx entry to the exports file 
for each directory exported, so that it looks like:

/etc/exports:
/datadisk/music	192.168.1.0/24(rw,no_subtree_check,fsid=1)
/datadisk/video		192.168.1.0/24(rw,no_subtree_check,fsid=2)
/datadisk/backup	192.168.1.0/24(ro,no_subtree_check,fsid=3)
...

If the same fsid is used more than once then the first directory with this fsid 
will be mounted! So using *different* fsids for each exported directory is 
essential!!!

So, my NFS works now as it should! 

Thanks to all who spent a thought on it!

Alex