NSM monitors the network to detect if hosts that held NLM locks on files have rebooted. When a host reboots, locks are automatically released, enabling the host to lock again.
NSM requires every client host to be configured to send sm_notify reboot notifications to NFS peers.
Once this configuration is done, there is no need to manually release any NLM locks, with the exception of locks that were made before upgrade to VAST Cluster 2.0.0 or a later release. Any locks that were made before upgrade to 2.0.0 will not be removed by NSM and can be released manually through theVAST Web UIorVAST CLI.
To enable sm_notify reboot notifications using a static IP network configuration, do this on each client host:
Define a local static IP on the network interface. For example:
$ cat /etc/sysconfig/network-scripts/ifcfg-bond0 # generated by configure_network.py DEVICE=bond0 NAME=bond0 TYPE=Bond BONDING_MASTER=yes ONBOOT=yes BOOTPROTO=none BONDING_OPTS="mode=balance-xor miimon=100 xmit_hash_policy=layer2+3" MTU=9216 IPADDR=192.0.2.20 NETMASK=255.255.255.0 GATEWAY= DNS1= PEERDNS=yes
Edit /etc/nfs.conf to enable
sm-notifyon the above configured IP:
$ cat /etc/nfs.conf ... [sm-notify] #debug=all # retry-time=900 # outgoing-port= outgoing-addr=192.0.2.20 # lift-grace=y
That's it! Now the client will send notifications on reboot and any files locked by the client will automatically be released.
Article is closed for comments.