Sauf par nécessité de rétro-compatibilité, il est conseillé d'utiliser la version NFS en version 4.2

NFSv4 vs NFSv3

The latest protocol of NFS is v4. It has minor versions: v4.2, v4.1, and v4.0. However, NFS Linux implementations generally support NFSv3 for backward compatibility.

NFSv3 requires supplementary services like rpcbind, mountd, lockd, and statd. Furthermore, the v3 protocol doesn’t mandate TCP implementation.

On the other hand, NFSv4 doesn’t depend on rpcbind, lockd, and statd as it has these functionalities built in. Only mountd is still used for exporting file shares, but not in the client-server connection. Hence, these services needn’t be exposed through a firewall. Moreover, NFSv4 has features like better security, reliability, enhanced client caching, and internationalization.

apt-get install nfs-kernel-server

Modifier le fichier /etc/nfs.conf. Désactiver la version 3 et activer la version 4 :

...
[nfsd]
# debug=0
# threads=8
# host=
# port=0
# grace-time=90
# lease-time=90
# udp=n
# tcp=y
vers3=n
# vers4=y
vers4.0=n
vers4.1=n
vers4.2=y
# rdma=n
# rdma-port=20049
...

Vérifier les versions de NFS supportées par le serveur :

cat /proc/fs/nfsd/versions 
-2 -3 +4 -4.0 -4.1 +4.2

Désactiver les service en lien avec NFSv3 :

systemctl mask --now rpc-statd.service rpcbind.service rpcbind.socket

Depuis le poste client, le montage échoue avec le message :

Source : partage NFSv4 erreur no such file or directory (askubuntu.com)

• Déployer un serveur NFS (redhat.com)
• NFSv4 sous Ubuntu/Debian (cyberciti.biz)
• NFS derrière pare-feu UFW