Hello,
We have FreeNAS-11.1-U5 with VMWare vCenter 6.5 / ESXi 6.5.0. Currently we are using NFS 3 but we would like to move to NFS 4.1.
NFSv4 is enabled (Services -> NFS) but when creating new datastore in vSphere it is attached in read-only mode. While looking at vmkernel log:
I’ve found VMWare thread related to the issue: https://communities.vmware.com/thread/517788
And there even appears to be some fixes on FreeBSD: https://www.mail-archive.com/freebsd-stable@freebsd.org/msg135292.html
There is also recent revision related to ReclaimComplete here:
Did anyone encounter the same issue? Does anyone has ESXi 6.5/6.7 working fine with NFS 4.1 on FreeNAS?
Thanks!
We have FreeNAS-11.1-U5 with VMWare vCenter 6.5 / ESXi 6.5.0. Currently we are using NFS 3 but we would like to move to NFS 4.1.
NFSv4 is enabled (Services -> NFS) but when creating new datastore in vSphere it is attached in read-only mode. While looking at vmkernel log:
Code:
2018-07-31T10:50:09.058Z cpu0:34830 opID=f6b6ea7a)NFS41: NFS41_VSIMountSet:402: Mount server: my-server.data, port: 2049, path: /mnt/rz2.1/zzz/sync, label: ds-nfs4, security: 1 user: , options: <none> 2018-07-31T10:50:09.058Z cpu0:34830 opID=f6b6ea7a)StorageApdHandler: 982: APD Handle Created with lock[StorageApd-0x4305abbc6140] 2018-07-31T10:50:09.059Z cpu2:33436)NFS41: NFS41ProcessClusterProbeResult:3865: Reclaiming state, cluster 0x4305abbc73c0 [0] 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)NFS41: NFS41FSCompleteMount:3582: Lease time: 120 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)NFS41: NFS41FSCompleteMount:3583: Max read xfer size: 0x20000 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)NFS41: NFS41FSCompleteMount:3584: Max write xfer size: 0x20000 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)NFS41: NFS41FSCompleteMount:3585: Max file size: 0x800000000000 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)NFS41: NFS41FSCompleteMount:3586: Max file name: 255 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)WARNING: NFS41: NFS41FSCompleteMount:3591: The max file name size (255) of file system is larger than that of FSS (128) 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)WARNING: NFS41: NFS41FSCompleteMount:3601: RECLAIM_COMPLETE FS failed: Not supported; forcing read-only operation 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)NFS41: NFS41FSAPDNotify:5651: Restored connection to the server my-server.data mount point ds-nfs4, mounted as 224813fb-f26022ab-0000-000000000000 ("/mnt/rz2.1/zzz/sync") 2018-07-31T10:50:09.061Z cpu0:34830 opID=f6b6ea7a)NFS41: NFS41_VSIMountSet:414: ds-nfs4 mounted successfully
I’ve found VMWare thread related to the issue: https://communities.vmware.com/thread/517788
And there even appears to be some fixes on FreeBSD: https://www.mail-archive.com/freebsd-stable@freebsd.org/msg135292.html
There is also recent revision related to ReclaimComplete here:
Code:
This patch along with r332790, r334492 and r336357 allow ESXi 6.7 NFSv4.1 mounts work ok. ESX 6.5 NFSv4.1 mounts do not work well, due to what I believe are violations of RFC-5661 and should not be used.
Did anyone encounter the same issue? Does anyone has ESXi 6.5/6.7 working fine with NFS 4.1 on FreeNAS?
Thanks!