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

• Problem

Due to a limitation on the length of the path name to backing store volumes, cold-installing

HP-UX 11i v3 fails in an HP VM guest. The install fails with the following error:

NOTICE: VxVM vxdmp V-5-0-34 added disk array OTHER_DISKS, datype =

OTHER_DISKS VxVM vxdisk ERROR V-5-1-5433 Device disk1_p2: init

failed: Device path not valid * smapi listener returned

"ACTION_FAILURE" for message "CREATE_GROUP" The configuration process

has incurred an error, would you like to push a shell for debugging

purposes? (y/[n])

The problem can also manifest itself after a cold install procedure, with any attempt to use

VxVM on a guest HP VM virtual device whose backing store path name is too long. This issue

will be fixed in a subsequent release of VxVM.

Workaround

Restrict the length of the path name to a backing store volume. If using VxVM volumes as

backing store, the combined number of characters in the volume group name and the volume

name must not exceed 9.

For all backing stores (including VxVM, LVM or raw disk), the full path name to the backing

store device or volume must not exceed 23 characters.

• Problem

While uninstalling VxVM using the swremove command, the following error message is

displayed:

vxdctl: Configuration daemon is not accessible

Workaround

You can ignore this message. The swremove command removes VxVM appropriately.

Utility Issues

• Problem

When devices are configured with native multipathing, rebooting certain VxVM commands

such as vxdisk scandisk takes a long time to complete.

Workaround

This issue is caused by broken or slow disk devices on the system. To identify broken disk

devices, enter the following command for all disks on the system:

dd if=/dev/disk/disk1 of=/dev/null bs=1024 count=10

The command normally returns within a few seconds. If the command takes more than 5

seconds for any disk on the system under an idle (No load) condition, that disk must be

replaced.

• Problem

VxVM supports volume lengths upto 256 TB. However, any 32-bit legacy applications that

use system calls such as seek, lseek, read, and write are limited to a maximum offset

that is determined by the operating system. This value is usually 2

-1 bytes (1 byte less than

2 terabytes).

Workaround

No workaround exists for this problem.

• Problem

The vxassist command does not add a mirror and a log when processing a command such

as the following:

22 Veritas Volume Manager 5.0 Release Notes