Managing Serviceguard NFS for Linux, July 2007

Installing and Configuring Serviceguard NFS for Linux
Configuring a Serviceguard NFS Package
Chapter 2 35
NFS_SERVICE_CMD[0]=/usr/local/cmcluster/pkg1/nfs.mon
Multiple instances of the monitor script can run on the same
node without any problems, and if a package fails over, only the
instance associated with that package is terminated.
If you do not want to run the NFS monitor script:
Comment out the NFS_SERVICE_NAME and NFS_SERVICE_CMD
variables. For example:
# NFS_SERVICE_NAME[0]=nfs1.monitor
3. If you want to start and monitor rpc.quotad daemon, set
QUOTA_MON to YES. For example:
QUOTA_MON=YES
If you do not want to start and monitor rpc.quotad daemon, set
QUOTA_MON to NO. For example:
QUOTA_MON=NO
Configuring Lock Migration Feature
The following steps need to be completed to use of the lock migration
feature:
1. In the package configuration file, set the
SERVICE_FAIL_FAST_ENABLED to “YES” for the NFS monitoring
service. Example:
SERVICE_NAME nfs1.monitor
SERVICE_FAIL_FAST_ENABLED YES
SERVICE_HALT_TIMEOUT 300
NOTE In RedHat, there are times when sending SIGKILL to the kernel
‘lockd’ thread might not release all the file locks and cause the failure
of the unmounting of filesystem. To force unmount of the filesystem,
the machine has to be rebooted. In such cases, it is recommended to
set SERVICE_FAIL_FAST_ENABLED to “YES” which reboots the
machine upon service failure.
In SLES, the sm directory does not consistenty update with the client
entries. This is due to the client entry being made for the first time
only after the system has booted. After a fail back of the package, the