Managing HP Serviceguard A.12.00.00 for Linux, June 2014

6.1.4.41 kill_processes_accessing_raw_devices
Specifies whether or not to kill processes that are using raw devices (for example, database
applications) when the package shuts down. Default is no. See the comments in the package
configuration file for more information.
6.1.4.42 File system parameters
A package can activate one or more storage groups on startup, and to mount logical volumes to
file systems. At halt time, the package script unmounts the file systems and deactivates each storage
group. All storage groups must be accessible on each target node.
For each file system (fs_name) you specify in the package configuration file, you must identify a
logical volume, the mount point, the mount, umount and fsck options, and the type of the file
system; for example:
fs_name /dev/vg01/lvol1
fs_directory /pkg01aa
fs_mount_opt "-o rw"
fs_umount_opt ""
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.
For an NFS-imported file system, see the discussion under fs_name (page 198) and fs_server
(page 198).
The parameter explanations that follow provide more detail.
6.1.4.43 concurrent_fsck_operations
The number of concurrent fsck operations allowed on file systems being mounted during package
startup.
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.44 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.
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.
6.1.4.45 fs_umount_retry_count
The number of umount retries for each file system.
Legal value is 1 or any greater number. The default is 1. Operates in the same way as
fs_mount_retry_count.
6.1 Choosing Package Modules 197