HP-UX Logical Volume Manager and MirrorDisk/UX Release Notes HP-UX 11i v3 (September 2010)

vgchange enhancement
The vgchange command now enables you make a volume group cluster aware (vgchange –c
y) even if the cluster daemon is not running. For more information, see vgchange(1M).
Deprecated or obsolete features
No LVM or MirrorDisk/UX features are deprecated or obsolete in the September 2010 release of
HP-UX 11i v3.
Known problems fixed in this version
The following table lists the known LVM and MirrorDisk/UX problems fixed in the September 2010
release of HP-UX 11i v3.
Table 1 LVM Fixes in HP-UX 11i v3 September 2010
DescriptionDefect ID
When vgextend is run on a physical volume belonging to an exported Version 2.x volume
group, the command fails and wipes out some LVM metadata upon failure. This causes
subsequent vgimport of the exported volume group to fail.
QXCR1000930924
After using vgversion to migrate a Version 2.2 volume group to a lower Version 2.x volume
group, if you deactivate the volume group (without performing a configuration change),
restore the first physical volume of the volume group with the Version 2.2 volume group
configuration file, and activate the volume group, a panic occurs.
QXCR1000994376
On successful completion, the vgversion command does not automatically back up the
configuration. Other configuration commands already do this.
QXCR1000994377
If you execute the vgchgid command on a large number of physical volumes, it can fail with
the Not enough space error message.
QXCR1000995258
The system will panic when the pvdisplay and pvmove commands are run at the same
time on a 1.0 volume group.
QXCR1000997427
The pvmove command displays incorrect primary path for an alternate link when more than
one physical volume or alternate link is specified as the destination physical volume.
QXCR1000998563
If using the default timeout value on a snapshot or its successor logical volume and there are
I/Os in progress on either the snapshot or its successor, changing the timeout value of the
snapshot logical volume can hang if the physical volumes that need to be accessed to achieve
data unsharing for the I/Os are unavailable.
QXCR1001002810
When write I/Os are in progress that require data unsharing on a space-efficient snapshot
logical volume with pre-allocated extents, if you run pvmove that involves movement of at
least some of these pre-allocated extents, the pvmove operation succeeds, but only performs
a partial movement. After the completion of pvmove operation, incorrect values are displayed
in the Current pre-allocated PE, Free PE, and Allocated PE fields for the
vgdisplay and pvdisplay output.
QXCR1001005207
When lvextend and vgextend are run simultaneously on the same volume group, both
the LVM commands hang until one of the commands is killed.
QXCR1001005212
When adding a physical volume to a shared Volume group using MORE in the HPVM cluster
environment, the vgextend command fails with the error message vgextend: Couldn't
install the physical volume pvname. The path does not specify a
valid physical volume.
QXCR1001008478
In some cases when the size of the physical volume is very large, the online vgmodify
operation for DLE shows an incorrect value in new disk size field. The new size of the physical
volume is reported as 0 in stead of the actual value.
QXCR1001009243
When deleting a snapshot that has one or more predecessors, and the operation requires
data unsharing, the delete operation can hang under low memory conditions.
QXCR1001011513
During volume group activation, some physical volumes might fail to attach. The result is that
some logical volumes are not available.
QXCR1001012753
Known problems fixed in this version 5