Summary:
Veritas Volume Manager  5.0 Rolling Patch 1 (RP1) for Linux, which should be installed on top of the base Volume Manager 5.0 release, is now available.  This patch can be applied either on Red Hat Enterprise Linux (RHEL 4) or on SUSE Linux Enterprise Server 9 (SLES9), and supports i686 and X86_64 architectures on Red Hat, as well as i586 and X86_64 on SUSE.

Refer to the list of incidents fixed in this patch below, as well as instructions for installation

To obtain this patch, see TechFile  http://support.veritas.com/docs/285609
 

Fixed Incidents:

619958      After encapsulating a SAN-connected root disk on an EMC CLARiiON CX700 array, a system panic occurred during booting when multiple paths were enabled. Systems with an encapsulated root disk on an Active/Passive array in explicit failover mode (A/PF array) failed to boot if more than one path was enabled. Systems with an encapsulated root disk on an Active/Passive array (A/P array) took a longer time than usual to boot.

771691 The vxrootmir command would not copy the Master Boot Record (MBR) to a root mirror disk. This behavior was generic to all arrays.

778352 Mirroring the root disk to a SAN boot disk could cause data corruption. This behavior was generic to all arrays.

Uncompress and untar the RPM files:

The tar file contains RPMs for multiple architectures for both Red Hat and SUSE platforms. The Veritas Volume Manager 5.0 general release packages must already be installed on the platform being patched.  Choose the correct RPMs for the correct system and architecture and install them with the rpm command, using these options:

The post-install script will not be able to unload the modules while they are in use and the Veritas Files System mounts are still active. There will be a warning message to this effect. A system reboot is recommended to make sure the scripts have no issues with checking kernel versions and the correct modules are applied. Once rebooted, the system will copy the correct modules from /etc/vx/kernel and load them without error so that the above warning will disappear. This installation and usage of the correct modules can be confirmed by comparing the files in /lib/modules/'uname -r'/veritas/vxfs to the /etc/vx/kernel modules (the module storage area).