Managing HP Serviceguard for Linux, Tenth Edition, September 2012

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 "ext2"
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.
The parameter explanations that follow provide more detail.
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).
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).
220 Configuring Packages and Their Services