HP-UX 11i v3 Installation and Update Guide, March 2009 (Update 4 Release)

Table A-1 Known Install and Update Problems (continued)
Description/ActionProblem
A message such as the following may be logged into dmesg during
VxVM operations:
"WARNING: VxVM vxio V-5-3-946
vol_disk_change_iopolicy:
Public region
policy specific open failed for c0t2d0 0x5000020
ret = 0xffffffff"
These messages are logged when internal or external USB devices
are detected on the system and when the minor number of the USB
devices collide with any of the other storage disks connected to the
system. This results in the corresponding disks (disks that have same
minor number as that of the USB devices) not being able to be opened
by VxVM.
In the above WARNING message, “open failed for cXtXdX”
indicates which disks will not function well under VxVM.
What To Do
No workaround exists for this problem at this time. HP and Symantec
are investigating possible solutions. Although the disks might work,
the behavior is unknown and not supported. VxVM is not supported
on systems that have USB devices connected at this point in time.
This co-existence issue is tracked by QXCR1000834043. VxVM will
be supported on systems that have USB devices once the fix for
QXCR1000834043 is available.
VxVM Not Supported On
Systems With USB Devices At
This Time
While updating from a previous OEUR to the HP-UX 11i v3
September 2008 OEUR and beyond, the following messages may be
logged onto the console:
*[902] Running "preinstall" script for fileset
"VRTSob.VEAS-FILESET".
- [902] kill: 1944: The specified process does
not exist.
*[367] Running "preinstall" script for fileset
"VRTSob.VEAS-FILESET
succeeded with 1 warning.
*[1394] Installing fileset
"VRTSob.VEAS-FILESET,r=3.3.837.0"
(841 of 1062).
What To Do
This is a harmless message. Installation is not affected. VRTSob will
start without any problem once the update is complete.
Update from Previous OEUR to
HP-UX 11i v3 September 2008 and
Beyond May Log Harmless
Message on Console Regarding
VRTSob
108 Known Problems and Troubleshooting