Veritas Volume Manager 5.0.1 Release Notes HP-UX 11i v3 (5900-0033, August 2011)

NOTE: For information on the Known Problems and Workarounds in VxVM 5.0 in the HP-UX
11i v3 operating system, see Veritas Volume Manager 5.0 Release Notes, HP-UX 11i v3, First
Edition, May 2008 available at http://www.docs.hp.com.
• Problem
HP-UX 11i v3 guests may panic while booting with virtual disks that have logical volume or
file backing stores with names that are 55 characters or greater.
Workaround
To avoid this panic and to prevent the guest from crashing, shorten the logical volume or
backing store names to less than 55 characters.
• Problem
If an ANSI C compiler is installed on a system before installing the 5.0.1 bundles, the following
swverify errors may be displayed after installing the 5.0.1 bundles.
==========================================
ERROR: Symlink "/usr/bin/cc" should have value "/usr/ccs/bin/cc" but
the actual value is "/opt/ansic/bin/cc".
ERROR: Fileset "OS-Core.C-KRN,l=/,r=B.11.31" had file errors.
==========================================
Workaround
You can ignore these error messages because these messages are harmless messages and
do not impact any functionality on the system.
• Problem
The vxddladm listsupport all command may not list all of the arrays used by DMP.
Workaround
To list all of the supported arrays in VxVM 5.0.1:
1. Run the vxddladm command:
# vxddladm addsupport all
The vxddladm addsupport all command is informational and harmless to run.
2. Run the vxddladm command:
# vxddladm listsupport all
• Problem
Deport operation on a shared disk group fails
With all primary paths inaccessible, the deport operation on a shared disk group fails to clear
the Page Request (PGR) keys as the DMP database is not up-to-date. The deport operation
succeeds but the PGR keys are not cleared as the DMP database is not updated to reflect the
inaccessibility of failed primary paths.
Workaround
Running the vxdisk scandisks command before the Disk Group (DG) deport operation
triggers DMP reconfiguration that updates the DMP database such that a disk is accessible
through active paths.
• Problem
I/O failures result in the disk failing flag
In some DMP failover scenarios, I/O retry causes the disk failing flag to be set, although there
is nothing wrong with the disks except for the failing flag.
Known Problems And Workarounds 17