Recommended NFS Mount Options

REQUIREMENTS

The combination of the mount options intr (Interrupt) and hard (Hard Mount) provide the best balance of data integrity and client stability in the event of a client disconnection from the server.
The tcp option ensures that TCP is used during the mount phase and data transfer, greatly speeding up mount times in some environments.
- Qumulo does not support NFS traffic over UDP
With modern Linux distributions, there is no need to specify most NFS mount options as the client will auto-negotiate the mount string with the server, including setting up a 1MB send/receive block size.
The Local Locks options listed below are provided for compatibility client software that requires some form of positive file locking but the use of NLM file locking is not desired.
READDIRPLUS, specified via the rdirplus mount option, allows more aggressive polling of metadata from directories and can greatly improve the performance of directory listing and "ls" operations on Macs.
- This is a default option on modern Linux distros

Run the following command on the client to list your current NFS mount options being used for all NFS mounts:

nfsstat -m

Mac Client

mount -t nfs -o rsize=65536,wsize=65536,intr,hard,tcp,rdirplus,readahead=128 your.qumulo.ip:/share /path/to/mountpoint

Mac Client: Local Locking Enforced

mount -t nfs -o rsize=65536,wsize=65536,intr,hard,tcp,locallocks,rdirplus,readahead=128 your.qumulo.ip:/share /path/to/mountpoint

Linux Client: Please note that modern Linux distributions auto negotiate a 1MB read/write block size (rsize/wsize of rsize=1048576).

mount -t nfs -o intr,hard,tcp your.qumulo.ip:/share /path/to/mountpoint

Linux Client: Local Locks Enforced

mount -t nfs -o intr,hard,tcp,local_lock=all your.qumulo.ip:/share /path/to/mountpoint

You should now know the recommended mount options when mounting a Qumulo cluster from a Mac or Linux client over NFS

Like what you see? Share this article with your network!