Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6212
If the package needs to run fsck on a large number of file systems, you
can improve performance by carefully tuning this parameter during
testing (increase it a little at time and monitor performance each time).
concurrent_mount_and_umount_operations
The number of concurrent mounts and umounts to allow during package
startup or shutdown.
Legal value is any number greater than zero. The default is 1.
If the package needs to mount and unmount a large number of file
systems, you can improve performance by carefully tuning this
parameter during testing (increase it a little at time and monitor
performance each time).
fs_mount_retry_count
The number of mount retries for each file system.
Legal value is zero or any greater number. The default is zero. The only
valid value for Red Hat GFS (see fs_type on page 213) is zero.
If the mount point is busy at package startup and
fs_mount_retry_count is set to zero, package startup will fail.
If the mount point is busy and fs_mount_retry_count is greater than
zero, the startup script will attempt to kill the user process responsible
for the busy mount point (fuser -ku) and then try to mount the file
system again. It will do this the number of times specified by
fs_mount_retry_count.
If the mount still fails after the number of attempts specified by
fs_mount_retry_count, package startup will fail.
This parameter is in the package control script for legacy packages.
fs_umount_retry_count
The number of umount retries for each file system. Replaces
FS_UMOUNT_COUNT, which is still supported in the package control script
for legacy packages; see “Configuring a Legacy Package” on page 262.
Legal value is 1 or (for filesystem types other than Red Hat GFS) any
greater number. The default is 1. Operates in the same way as
fs_mount_retry_count (see page 212).