This section outlines how to use the highly available NFS service from an NFS client. It covers NFS clients using NFS versions 3 and 4.
To connect to the highly available NFS service with an NFS version 3 client, make sure to use the virtual IP address to connect to the cluster, rather than a physical IP configured on one of the cluster nodes' network interfaces. NFS version 3 requires that you specify the full path of the NFS export on the server.
In its simplest form, the command to mount the NFS export with NFSv3 looks like this:
mount -t nfs 10.9.9.180:/srv/nfs/engineering /home/engineering
For selecting a specific transport protocol (proto) and maximum read and write request sizes (rsize and wsize):
mount -t nfs -o proto=udp,rsize=32768,wsize=32768 \ 10.9.9.180:/srv/nfs/engineering /home/engineering
For further NFSv3 mount options, consult the nfs man page.
IMPORTANT: Connecting to the NFS server with NFSv4 will not work unless you have configured an NFSv4 virtual file system root. For details on how to set this up, see NFSv4 Virtual File System Root.
To connect to a highly available NFS service, NFSv4 clients must use the floating cluster IP address (as with NFSv3) , rather than any of the cluster nodes' physical NIC addresses. NFS version 4 requires that you specify the NFS export path relative to the root of the virtual file system. Thus, to connect to the engineering export, you would use the following mount command (note the nfs4 file system type):
mount -t nfs4 10.9.9.180:/engineering /home/engineering
As with NFSv3, there are a multitude of mount options for NFSv4. For example, selecting larger-than-default maximum request sizes may be desirable:
mount -t nfs4 -o rsize=32768,wsize=32768 \ 10.9.9.180:/engineering /home/engineering