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

[Joost Roeleveld]

On Sunday 29 June 2014 21:34:07 Alexander Puchmayr wrote:
> 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
> $
>
> [Poseidon is my server at 192.168.1.6, the client is at 192.168.1.2]
>
> Server disk to be exported is a ~9TB raid array with XFS.
>
> I'm using nfs3 with ACL and no idmapd; nfs4+ is not compiled into kernel
> (neither on client nor on server); Why it is trying nfs4 first as seen in
> the log above I don't know. nfs-utils has been compiled with USE=-nfsv4
>
> Server has kernel version 3.12.21-gentoo-r1and net-fs/nfs-utils-1.2.9
> installed. As both clients and server are not accessable from outside, no
> firewalls are installed.
>
> What I checked:
> /etc/exports:
> /datadisk               192.168.1.0/24(rw,async,subtree_check)
>
> portmapper, nfs-services are running normal, as far I can see.
>
> Does anyone have any suggestion?

I have this occasionally due to the backup system I am using:
- stop the nfs export
- umount the filesystem
- take LVM snapshot
- remound filesystem
- re-enable the nfs export

When that happens, I run the following on the server:
# exportfs -au && sleep 1 && mount -a && sleep 1 && exportfs -r

The sleeps are necessary, without them, it doesn't always work.

--
Joost