Managing Serviceguard Eighteenth Edition, September 2010

Table 7-3 Types of Changes to Packages (continued)
Required Package StateChange to the Package
Package should not be running (unless you are only changing
fs_umount_opt).
Changing file-system options other than fs_umount_opt may cause
problems because the file system must be unmounted (using the existing
fs_umount_opt) and remounted with the new options; the CAUTION
under “Remove a file system: modular package” applies in this case as
well.
If only fs_umount_opt is being changed, the file system will not be
unmounted; the new option will take effect when the package is halted
or the file system is unmounted for some other reason.
Change a file system: modular
package
Package can be running.Add a file system: modular
package
Package must not be running.Add or change a file system:
legacy package
Package should not be running.
CAUTION: Removing a file system may cause problems if the file
system cannot be unmounted because it's in use by a running process.
In this case Serviceguard kills the process; this could cause the package
to fail.
Remove a file system: modular
package
Package must not be running.Remove a file system: legacy
package
Package can be running.
These changes in themselves will not cause any file system to be
unmounted.
Change
concurrent_fsck_operations,
concurrent_mount_and_umount_operations,
fs_mount_retry_count,
fs_umount_retry_count: modular
package
Package must not be running.Change
concurrent_fsck_operations,
concurrent_mount_and_umount_operations,
fs_mount_retry_count,
fs_umount_retry_count: legacy
package
Package can be running.Change
kill_processes_accessing_raw_devices:
modular package
Package must not be running.Change
kill_processes_accessing_raw_devices:
legacy package
Package can be running.Add a vxvm_dg or cvm_dg:
modular package
394 Cluster and Package Maintenance