Managing Serviceguard Eighteenth Edition, September 2010

File system parameters
A package can activate one or more storage groups on startup, and 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. (CVM disk groups must be accessible on all nodes in the cluster).
For each local file system you specify in the package configuration file (fs_name
(page 307)), you must identify a logical volume, the mount point, the mount, umount,
and fsck options and type of the file system; for example:
fs_name /dev/vg01/lvol1
fs_directory /pkg01aa
fs_mount_opt "-o rw"
fs_umount_opt "-s"
fs_fsck_opt "-s"
fs_type "vxfs"
A logical volume can be created in an LVM volume group, a Veritas VxVM disk group,
or a Veritas CVM disk group. Logical volumes can be entered in any order, regardless
of the type of storage group. The parameter explanations that follow provide more
detail.
For an NFS-imported filesystem, see the discussion under fs_name (page 307) and fs_server
(page 308).
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 filesystems, 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 filesystems, you can
improve performance by carefully tuning this parameter during testing (increase it a
little at time and monitor performance each time).
306 Configuring Packages and Their Services