Managing Serviceguard NFS for Linux, July 2007

Serviceguard NFS for LINUX Introduction
How the Control and Monitor Scripts Work
Chapter 1 19
Starting File Lock Migration
If you call the NFS control script with the
lock_migration:<IP_address> parameter after enabling the File Lock
Migration feature, the control script does the following:
• Populates the /var/lib/nfs/sm directory on SLES and
/var/lib/nfs/statd/sm directory on RedHat with the Status
Monitor entries from the configured holding directory of the package,
and subsequently removes the entries from the holding directory.
• Kills any running copy of the NFS File Lock Migration
synchronization script, nfs.flm.
• Restarts the lockd and sm-notify on SLES and rpc.statd on
RedHat using package IP. Restarting this daemon triggers a crash
recovery notification event, whereby sm-notify/rpc.statd sends
crash notification messages to all clients listed in the
/var/lib/nfs/statd/sm directory on RedHat and
/var/lib/nfs/sm directory on SLES.
• Starts the File Lock Migration synchronization script, which
periodically copies the sm directory entries to the holding directory.
Halting the NFS Services
When called with the stop parameter, the control script does the
following:
• Removes the package IP address from the LAN card on the current
node.
• The package control script invokes the toolkit.sh to run the NFS
script and to halt the NFS related process.
• The NFS script un-exports all file systems associated with the
package so that they can no longer be NFS-mounted by clients.
• The NFS script halts the monitor process.
• The NFS script halts the File Lock Migration synchronization script
if you enable the File Lock Migration feature. The NFS daemons are
also halted to unmount the filesystem.
• Unmounts each file system associated with the package.
• Deactivates each volume group associated with the package.