Managing Serviceguard NFS for Linux, July 2007

Installing and Configuring Serviceguard NFS for Linux
Configuring a Serviceguard NFS Package
Chapter 238
Number of seconds between the attempts of the script to copy
files from the /var/lib/nfs/sm directory on SLES and
/var/lib/nfs/statd/sm on RedHat into the holding directory,
specified by NFS_FLM_HOLDING_DIR. The default value of this
parameter is five seconds.
An example for this parameter is as follows:
PROPAGATE_INTERVAL=5
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 RedHat 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 failsover 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.