Managing Serviceguard NFS for Linux, March 2009

NOTE: The NFS client may not receive a crash notification if it sends an initial lock
request to the NFS server and during the interim, the NFS package failsover to an
adoptive node before the FLM script copies the /var/lib/nfs/statd/sm entry on
Red Hat and /var/lib/nfs/sm entry on SLES for this client to the package holding
directory. Hence the client may not reclaim the lock once the NFS package fails over to
the adoptive node.
The probability of this occurring within the default time interval between copies is
extremely low as the SM file copy interval is very short (by default, five seconds). You
can reduce the probability further by configuring the time interval to a value lower than
the default.
d. NFS_FLM_MONITOR:
To monitor the file lock migration script (nfs.flm) by the NFS monitor script
(nfs.mon), set the NFS_FLM_MONITOR variable to “YES”. The default value is NO.
Setting this parameter to “YES” ensures that the file lock state files are being copied
into holding directory successfully.
e. NFS_FLM_RESTART:
Number of times the monitoring script should attempt to restart the file lock migration
script (nfs.flm) if it fails. The default value is 4.
NOTE: To use the lock migration feature, the user has to do all the configurations
specified above and also consider all the limitations of the lock migration feature
mentioned in the section on See section,“Limitations of the NFS File Lock Migration
Feature” (page 8).
Creating the Serviceguard Binary Configuration File
The following step must be executed to create a Serviceguard Binary Configuration file:
1. Use the cmapplyconf command to verify the content of your cluster and package
configuration and copy the binary configuration file to all the nodes in the cluster.
In the following example, the cluster configuration file is /usr/local/cmcluster/
cluster.conf. On your system, use the names of your own cluster configuration and
package configuration files.
# cmapplyconf -v -C /usr/local/cmcluster/cluster.conf -P \ /usr/local/
cmcluster/pkg01/pkg01.conf
Housekeeping Suggestions
After the NFS toolkit is installed, the shell scripts are located in /usr/local/cmcluster/
nfstoolkit and the binary file is located in /usr/bin on your Linux platforms. It is
recommended that you set up directories to keep your various package and script files grouped
for organization. Set up one directory for each package and keep the associated configuration
and monitoring scripts in that directory.
Configuring a Modular Serviceguard NFS Package
To configure a Modular NFS package, complete the following tasks:
• Editing the Package Configuration file (pkg.conf)
• Creating the Serviceguard binary configuration file
Configuring a Modular Serviceguard NFS Package 27