This article was last edited over 3 years ago. Information here may no longer be accurate. Please proceed with caution, and feel free to contact me.
These steps are for configuring an NFS Linux server on Ubuntu.
sudo apt-get install nfs-kernel-server
Check to see if NFS is running.
sudo systemctl status nfs-kernel-server
Create a directory to serve via NFS.
sudo mkdir -p /srv/nfs
/etc/exports file. In my case, I am serving
/srv/nfs directory to any machine on my network.
You may read about the
# /etc/exports /srv/nfs 192.168.0.0/24(sync,no_subtree_check,insecure)
Reload the NFS export configuration now that our export is defined.
sudo exportfs -ra
You may disable versions of NFS by editing
This would disable NFSv3.
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 3"
This would disable NFSv4.
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 4"
Restart the appropriate services to ensure the changes take effect.
sudo systemctl restart nfs-config sudo systemctl restart nfs-kernel-server
rpc.mountd on your
server to verify that your configuration is being used.
$ ps ax | grep rpc.mountd 3625 ? Ss 0:00 /usr/bin/rpc.mountd --manage-gids --no-nfs-version 3
You can use
showmount to confirm your client can see
the NFS shares.
$ sudo showmount -e 192.168.0.169 Export list for 192.168.0.169: /srv/nfs 192.168.0.0/24
You can mount the NFS share like so.
sudo mount \ -t nfs \ -o vers=4 \ 192.168.0.169:/srv/nfs /mnt/tmp
vers=4 option is not required, but is helpful in
ensuring that the server may have disabled a certain version.
If the server disables version 3 or 4, then the client should be rejected if it attempts to use that version.
See here an example where the client attempts to use an NFS protocol version that has been disabled by the server.
$ sudo mount -t nfs -o vers=3 192.168.0.169:/srv/nfs /mnt/tmp mount.nfs: Protocol not supported