Veritas Volume Manager 5.0 Release Notes HP-UX 11i v3 (5992-1952, August 2011)

• Problem
When all failed paths to the storage are restored, DMP automatically re-discovers them.
However, you would have to run the vxdctl enable command for VxVM/CVM to get the
disks back online. If the paths were restored before the reboot happens, then as part of boot,
device discovery would happen automatically. However, if the paths are restored after the
reboot, then you have to run vxdctl enable command to have VxVM rescan and rediscover
the failed devices. Also, if some operation had failed due to above reason, the operation
needs to be retried after discovery of device.
Workaround
VxVM and CVM does not automatically bring back the disks to online state. You must manually
run the vxdctl enable command. There is no other workaround available for this problem.
• Problem
There is no option in the vxddladm command to display the current naming scheme.
Workaround
The naming scheme that is in operation can be deduced from the output of the vxdisk list
command.
• Problem
The vxdiskadm command displays error V-5-1-9764 when excluding devices.
• Workaround
The vxdiskadm operation displays error V-5-1-9764 if a vendor and product ID combination
are specified to exclude devices from multi-pathing. This error is harmless and can be ignored.
The error is not seen if controller or device names are specified instead.
• Problem
Specifying an enclosure to the vxdmpadm getportids command.
Workaround
The enclosure attribute should be used to specify an enclosure name to the vxdmpadm
getportids command, instead of the enclr attribute that is shown in the Veritas Volume
Manager Administrator’s Guide and the vxdmpadm(1M).
• Problem
The VxVM configuration daemon, vxconfigd, can dump core under rare conditions if the
vxdctl enable command is run on a system with an HDS array.
Workaround
No workaround exists for this problem.
Device Issues
The following device issues are known:
• Problem
If a disk that is to be placed within the control of the Veritas Volume Manager, and was
previously used for a file system, VxVM cannot initialize the disk. VxVM recognizes such disks
as FS_wholedisk.
Workaround
If the disk was previously used for a file system, you must destroy the file system before placing
the disk under VxVM control. To destroy a file system, run the following commands:
26 Veritas Volume Manager 5.0 Release Notes