Veritas Volume Manager 5.1 SP1 Release Notes HP-UX 11i v3 (5900-1518, August 2011)

vxdg ERROR V-5-1-585 Disk group dgnew: cannot create: Disk for disk
group not found
This issue can occur if the naming scheme on the slave node where the command was issued
is the operating system's native scheme whereas the creation mode uses the new naming
scheme.
Workaround
You can create the shared disk group from the slave node by changing the naming scheme
to the operating system's native scheme while in the "Legacy" mode.
• Problem
After you initialize a disk that is under the operating system's native LVM control and not under
VxVM control by using the pvcreate path_to_physical_disk command, when the
vxdisk list disk_name command is issued for the first time, an error similar to the
following may be displayed:
VxVM vxdisk ERROR V-5-1-539 Device xp10240_0263: get_contents failed:
Disk device is offline
Also, the flags field (displayed by the vxdisk command) is incorrectly populated. However,
in the next instantiation of the same command, VxVM does not produce an error and the flags
are correctly populated with the LVM tag.
Workaround
Issue the vxdisk list disk_name command a second time.
• Problem
VxVM utilities may fail with the following error message:
Memory allocation failure
This error implies that there is insufficient memory for the vxconfigd daemon. A program's
data segment size is enforced by the operating system tunable maxdsiz. The default value
of maxdsiz is 1 GB. With this default maxdsiz value, the vxconfigd daemon can allocate
a maximum of 1 GB of memory.
Workaround
You might need to increase the operating system maxdsiz tunable's value appropriately to
increase the data storage segment for the programs.
See the maxdsiz(5) manual page for more information.
After increasing the value, you must stop and restart the vxconfigd daemon. Depending on
the maxdsiz tunable value, vxconfigd can allocate a maximum of up to 2 GB of memory
on PA machines, and 4 GB of memory on IA machines.
• Problem
Thin reclamation on disks with the hpdisk format is not supported. An attempt to perform
reclamation on such disks automatically aborts.
Workaround
There is no workaround for this issue.
• Problem
If the LUN is larger than 1 TB and the system is using Tachyon HBAs, the vxdisksetup
command fails to initialize the LUN to have the cdsdisk format and displays an error similar
to the following:
VxVM vxdisk ERROR V-5-1-5433 Device disk_name: init failed:
Disk is not useable, bad format
14 Veritas Volume Manager 5.1 SP1 Release Notes