IN THIS ARTICLE
Outlines the recommended NFS mount options for both Mac and Linux
REQUIREMENTS
- Cluster running Qumulo Core
NOTE: Qumulo currently only supports NFSv3 protocol for the following recommended NFS mount options.
OVERVIEW
- 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.
- 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
- 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.
DETAILS
Verify Current NFS Mount Options
Run the following command on the client to list your current NFS mount options being used for all NFS mounts:
nfsstat -m
Recommended Mount Options
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 with 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 with Local Locks Enforced
mount -t nfs -o intr,hard,tcp,local_lock=all your.qumulo.ip:/share /path/to/mountpoint
RESOLUTION
You should now know the recommended mount options when mounting a Qumulo cluster from a Mac or Linux client over NFS
ADDITIONAL RESOURCES
Like what you see? Share this article with your network!
Comments
1 comment
Hey Joe, thanks in advance for this post.
For couple days I was trying connect a Windows Server NFS volume in mac computers. ( A fck issue in FCPX that not allow store libraries in SMB Windows Volumes)
NFS Windows with OS/X it's not so simple. When connected via GUI, don't work - can't write files, make some errors.
When I tried via command line, appear that works fine, but everytime that I open a FCPX project, it don't open and show a messase that volume was disconnected.
Well I use same parameters that you show here for mac clients and it working fine now. I can access my NFS (from windows server) and it's working fine.
Thanks
João Ricardo
Please sign in to leave a comment.