Wondering if anyone else hit this issue, but we are running a custom FSAL with nfs-ganesha. It mounts fine with CentOS 7.2, 7.5 and Ubuntu 16.04 clients, but CentOS 7.6 clients give stale file handle on mount. I went through the changelog for CentOS 7.6 and nothing stood out NFS client related, but have tried several different 7.6 client VMs and they all fail to mount.
Any suggestions? The only options we typically use on mount is timeo=9000,noatime but those are not absolutely necessary and without any mount options CentOS 7.6 still fails to mount.
CentOS 7.6 (fail): [root@dhcp-12-253 ~]# mount nfstestvm1:/nfstest1 /mnt/nfstest1 -v
mount.nfs: timeout set for Tue Mar 26 11:13:51 2019
mount.nfs: trying text-based options 'vers=4.1,addr=172.30.15.146,clientaddr=172.30.13.253'
mount.nfs: mount(2): Stale file handle
CentOS 7.5 (success): [root@dhcp-12-248 ~]# mount nfstestvm1:/nfstest1 /mnt/nfstest1 -v
mount.nfs: timeout set for Tue Mar 26 11:16:12 2019
mount.nfs: trying text-based options 'vers=4.1,addr=172.30.15.146,clientaddr=172.30.13.248' [root@dhcp-12-248 ~]#
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Wondering if anyone else hit this issue, but we are running a custom FSAL with nfs-ganesha. It mounts fine with CentOS 7.2, 7.5 and Ubuntu 16.04 clients, but CentOS 7.6 clients give stale file handle on mount. I went through the changelog for CentOS 7.6 and nothing stood out NFS client related, but have tried several different 7.6 client VMs and they all fail to mount.
Any suggestions? The only options we typically use on mount is timeo=9000,noatime but those are not absolutely necessary and without any mount options CentOS 7.6 still fails to mount.
CentOS 7.6 (fail):
[root@dhcp-12-253 ~]# mount nfstestvm1:/nfstest1 /mnt/nfstest1 -v
mount.nfs: timeout set for Tue Mar 26 11:13:51 2019
mount.nfs: trying text-based options 'vers=4.1,addr=172.30.15.146,clientaddr=172.30.13.253'
mount.nfs: mount(2): Stale file handle
CentOS 7.5 (success):
[root@dhcp-12-248 ~]# mount nfstestvm1:/nfstest1 /mnt/nfstest1 -v
mount.nfs: timeout set for Tue Mar 26 11:16:12 2019
mount.nfs: trying text-based options 'vers=4.1,addr=172.30.15.146,clientaddr=172.30.13.248'
[root@dhcp-12-248 ~]#