3.1.2 MxFS-Linux Administration Guide

Chapter 5: Other Configuration Information 44

The following command verifies that clients on the 99.10.210.100 network

can now access the shared data:

# ls -l /mnt/data1

total 1

drwxr-xr-x 2 root root 48 Mar 24 00:32 dir1/

-rw-r--r-- 1 root root 0 Mar 24 00:32 file1

-rw-r--r-- 1 root root 0 Mar 26 12:29 file2

-rw-r--r-- 1 root root 0 Mar 24 00:32 file3

Using the NLM Protocol

NLM is the locking protocol used by NFS. By default, it is disabled when

MxFS is installed. If necessary, NLM can be enabled; however, you should

be aware of the following caveat:

• File locks granted by the NFS server are cluster-coherent. When a

failover occurs, the locks are released by the original server and the

client automatically reclaims them on the new server (the backup

node). However, during the period after the lock is released, another

client or application may compete for and win the lock. Some NFS

clients will return an error to the client applications if the lock cannot

be reclaimed. Other clients (for example, the Linux 2.6 NFS client) will

not return any error. If no error is returned by the client, the

application may proceed under the false assumption that the lock has

been granted. Data corruption may be the result.

To prevent this situation, locking should be enabled only if your

clients are partitioned so that all clients needing a particular lock are

using the same Virtual NFS Service IP address. If a failover occurs, all

of the clients will lose their locks. They can then reclaim those same

locks on the new node without conflicts from outside clients.

The mxnlmconfig command is used to enable or disable NLM locking in

the cluster.

NOTE: The change takes place immediately and may affect clients.