NOTE:

•If the system is configured in EBN (Enclosure Based Naming) scheme, then list_expander might not show the correct list. Change the mode to Operating System Native (OSN) naming scheme by running the vxddladm. See vxddladm(1M) manpage for more information on changing the naming scheme.

•The following circumstance may cause list_expander to halt:

When processing information, list_expander uses the libc function ftw, see ftw(3C), to recursively descend the directory hierarchy.

When ftw encounters a directory containing a large number of files, all of the descendent files are processed recursively. This can cause stack size problems. For example, if the directory contained 400,000 files, the stack size must be at least 51.2 MB to support the number of recursive function calls (400,000 calls x 128 bytes/stack frame), since each ftw call allocates a stack frame of 128 bytes. In this case it is wise to allocate additional space - 64 MB is a better stack size choice.

If the stack size is not large enough, list_expander is killed due to a stack growth failure. To avoid this situation, you must configure the kernel tunable maxssiz accordingly. See the kctune(1M) manpage for more information on tuning kernel parameters.

The above information is based on the HP-UX 11i v1 ftw() libc function. The behavior of ftw() between releases or patch versions of HP-UX may change. Consider this information indicative of the potential setting required; it must not be considered authoritative.

The file system volume sizes in the recovery image can be modified when the recovery image is installed. By default, Ignite-UX ensures that there is 10 percent free space for each volume, and modifies the file system volume size accordingly. If you do not want Ignite-UX to modify the file system volume sizes automatically, add

init _hp_ignore_sw_impact=1

to your /var/opt/ignite/recovery/latest/system_cfg file, or to the /var/opt/ignite/clients/client/recovery/latest/system_cfg file.

Verifying recovery image results

During a system recovery, Ignite-UX by default restores the system to the state it was in when the recovery image was created. Ignite-UX is a general-purpose installation tool. It modifies many system configuration files if changes from the recovery configuration are required, such as increasing volume sizes.

When you run make_[tapenet]_recovery, system configuration information is gathered and saved in configuration files that are used later when the system is recovered. During the system recovery you are allowed to make changes to this information, and Ignite-UX makes the appropriate changes to the system configuration. If you do not make any changes, Ignite-UX simply reapplies the same information, and there must be no change to the system after recovery.

Most of the system configuration files that Ignite-UX will modify are listed in the script, /opt/ ignite/data/scripts/os_arch_post_l. The os_arch_post_l script checks for the system recovery case by checking the $RECOVERY_MODE variable. When this variable is TRUE, the os_arch_post_l script causes some configuration files to be protected from modification by using the "save_file" function. The os_arch_post_l script uses the "merge_file" function on files that Ignite-UX knows how to merge information into.

The files operated on by "merge_file", as well as those that have a commented out "save_file" line, are likely to be modified by Ignite-UX. Comments in the file explain any exceptions.

Because the list of files modified by Ignite-UX may change from release to release, it is best to look at the os_arch_post_l file on your system to see which files are saved as-is and which are merged with information from the Ignite-UX configuration files.

System recovery 199