IN THIS ARTICLE
- Outlines how to mount with the "local lock" option of your NFS client for Qumulo Core 2.5.1 and below
- Cluster running Qumulo Core
Qumulo Core version 2.5.1 and above now supports the NLM protocol for locking over NFS. If you are running a version of Qumulo Core prior to 2.5.1 and require NLM for your workflows, please upgrade to 2.5.1 or above.
If you are running a version prior to 2.5.1, do not wish to/cannot upgrade, and are having trouble with applications requesting locks, please follow the guidance below.
Certain applications may request locks on files that reside on a Qumulo NFS export, and either hang or otherwise behave unexpectedly. For example, one such known application is Commvault Backup, which will attempt to acquire a lock over NFS before running a backup job.
Mounting with the the "local lock" option of your NFS client as outlined below, should allow the client application to acquire a local lock (one which is only applicable to the local client machine). The application should then be able to perform its task(s) unhindered. However, there is a risk that other network clients accessing the same files simultaneously can overwrite them. This may or may not be problematic depending on your specific workflow.
Below is an example NFS mount command for Linux and Mac OS X clients (where qumulo is the cluster hostname/DNS name and /production is the path to the NFS export). For information on configuring these options with automount/autofs, please consult the autofs documentation applicable to your OS, or contact the Qumulo Care team.
Mac OS X
mount -t nfs -o locallocks qumulo:/production /path/to/mountpoint
mount -t nfs -o local_locks=all qumulo:/production /path/to/mountpoint
You should now be able to successfully mount with the "local lock" option of your NFS client using the details above.
Like what you see? Share this article with your network!