Print Email PDF

Recommended NFS Mount Options

  1. Qumulo Care
  2. Qumulo Administration

IN THIS ARTICLE

This article explains the recommended NFS mount options for macOS and Linux. For more information, see Enabling and Using NFSv4.1 on a Qumulo Cluster and Managing File Access Permissions Using NFSv4.1 Access Control Lists (ACLs).

DETAILS

Verify Current NFS Mount Options

To list the NFS mount options currently used for all NFS mounts, use the following command.

nfsstat -m

Recommended Mount Options for macOS 11 (and Higher)

macOS 11 (and higher) supports 1 MB read and write blocks. This can help improve NFS client performance.

Client with Server-Side Network Lock Manager (NLM) Enabled

mount -t nfs \
  -o vers=3,intr,hard,tcp,rdirplus,readahead=128,rsize=1048576,wsize=1048576 \
  qumulo.hostname:/share /path/to/mountpoint

Client with Local Locking Enforced

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

Note: Mac clients don't support NFSv4.1.

Recommended Mount Options for macOS 10.15 (and Lower)

Client with Server-Side Network Lock Manager (NLM) Enabled

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

Client with Local Locking Enforced

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

Note: Mac clients don't support NFSv4.1.

Recommended Mount Options for Linux

Notes

  • In Linux kernel 5.3 (and higher), the nconnect option allows multiple TCP connections for a single NFS mount.
    Note: Currently, the maximum number of concurrent TCP connections is 16.
  • In Linux kernel 2.6.25 (and higher), the intr and nointr mount options are deprecated. If you use the hard option on modern Linux kernels, you must use the kill -9 (SIGKILL) command to interrupt a stuck NFS mount.

Client with NFSv3 and NLM Locking Enabled

mount -t nfs \
  -o vers=3,tcp,nconnect=16 \
  qumulo.hostname:/share /path/to/mountpoint

Client with NFSv3 and NLM Locking Disabled and Local Locking Enforced

mount -t nfs \
  -o vers=3,tcp,local_lock=all,nconnect=16 \
  qumulo.hostname:/share /path/to/mountpoint

Client with NFSv4.1 and AUTH_SYS Authentication.

Note: AUTH_SYS authentication uses UIDs and GIDs.

mount -t nfs \
  -o vers=4.1,tcp,sec=sys,nconnect=16 \
  qumulo.hostname:/share /path/to/mountpoint

ADDITIONAL RESOURCES

QQ CLI: NFS Exports

Articles in this section

See more
Was this article helpful?
3 out of 4 found this helpful

Comments

2 comments

Sort by Date Votes
  • Avatar
    Jr

    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

    0
  • Avatar
    Matt Kochanek

    Hi Qumulo, now that NFS 3 and 4 is supported, I think you should add the NFS version to recommended mount options. 

    0

Please sign in to leave a comment.

Have more questions?
Open a Case
Share it, if you like it.