Managing HP Serviceguard A.11.20.10 for Linux, December 2012

fs_fsck_opt ""
fs_type "ext3"
A logical volume must be built on an LVM volume group. Logical volumes can be entered in any
order.
A gfs file system can be configured using only the fs_name, fs_directory, and
fs_mount_opt parameters; see the configuration file for an example. Additional rules apply for
gfs as explained under fs_type.
NOTE: Red Hat GFS is not supported in Serviceguard A.11.20.00.
For an NFS-imported file system, see the discussion under fs_name (page 181) and fs_server
(page 182).
The parameter explanations that follow provide more detail.
6.1.4.38 concurrent_fsck_operations
The number of concurrent fsck operations allowed on file systems being mounted during package
startup. Not used for Red Hat GFS (see fs_type).
Legal value is any number greater than zero. The default is 1.
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).
6.1.4.39 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) is zero. Red Hat GFS is not
supported in Serviceguard A.11.20.00.
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.
6.1.4.40 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”
(page 225).
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.
6.1.4.41 fs_name
This parameter, in conjunction with fs_directory, fs_type, fs_mount_opt,
fs_umount_opt, and fs_fsck_opt, specifies a filesystem that is to be mounted by the package.
Replaces LV, which is still supported in the package control script for legacy packages.
fs_name must specify the block devicefile for a logical volume.
6.1 Choosing Package Modules 181