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

to signals or interact with native interprocess communication. This scenario can result in the
following problems:
◦ The node becomes unavailable for VxVM administrative commands.
◦ In a clustered or HA environment where Veritas Cluster Server agents need to communicate
with vxconfigd daemon to determine the health of VxVM components, service groups
will time out and fail.
Workaround
No workaround exists for this problem.
• Problem
A disk group is disabled if the vxdg init command is used to create it from a set of disks
that have pre-existing private regions differing in size. This may occur if the disks belonged
to disk groups in the older releases of VxVM.
Workaround
Reinitialize the disks before creating the disk group (for example, by using the vxdisk-f
init command), or to run the vxdg adddisk command to add the disks to the disk group
after it has been created.
• Problem
It is not possible to use the vxresize command to change the size of a component volume
of a volume set that has an unmounted file system. This is because the extendfs command,
for extending unmounted file systems, is not supported on volume sets.
Workaround
No workaround exists for this problem.
• Problem
Resizing volumes fails in a remote mirror configuration having detached remote plexes.
Workaround
If a volume in a Remote Mirror configuration has detached plexes, at a remote site, you can
use the following procedure to resize it:
1. Turn off the allsites attribute for the volume:
# vxvol -g diskgroup set allsites=off volume
2. Remove the detached plexes
# vxassist -g diskgroup remove mirror volume
plexnames=plex1,plex2,...
3. Use the vxresize command to resize the volume.
4. When the remote site comes up, complete the following steps:
a. Replace the removed plexes using the storage device at the remote site:
# vxassist -g diskgroup mirror volume nmirror=N \site:remote_site_name
b. Turn on the allsites attribute for the volume:
# vxvol -g diskgroup set allsites=on volume
• Problem
A message such as the following is displayed if an attempt is made to open a volume at boot
time before any disk group has been imported:
VxVM vxio V-5-0-23 Open on an spurious volume device (hex_id) encountered.
This device may be valid, but has not yet been configured in the kernel.
Workaround
24 Veritas Volume Manager 5.0 Release Notes