HP-UX Logical Volume Manager and MirrorDisk/UX Release Notes (September 2009)

Changed Features
The following features have changed in the September 2009 release of LVM and MirrorDisk/UX:
pvmove Enhancements
The pvmove command supports the following new features for Version 2.0 and higher volume
groups:
Online rebalancing
Enables you to automatically rebalance the space for a single volume, a set of logical volumes,
or all physical volumes belonging to the volume group. For example, to rebalance the space
on volume group vg02, enter:
# pvmove -a /dev/vg02
Freeing up physical volumes in a volume group
Enables you to move all the allocated extents from a single physical volume or set of physical
volumes of a volume group to the remaining physical volumes, keeping the space on the
remaining physical volumes balanced. For example, to move all extents on physical volume
/dev/rdisk/disk32 to the remaining physical volumes in the volume group, enter:
# pvmove -a -f /dev/rdisk/disk32
NOTE: Before performing online rebalancing with pvmove, you can preview the operation by
using the p option. In addition, you can use the s option to generate a preview summary
report of the requested rebalance action without actually performing any move.
For more information, see pvmove(1M).
Deprecated or Obsolete Features
No LVM or MirrorDisk/UX features are deprecated or obsolete in the September 2009 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
2009 release of HP-UX 11i v3.
Table 1 LVM Fixes in HP-UX 11i v3 September 2009
DescriptionDefect ID
Some messages displayed by the vgchange command are not localized and appear in
English for non C locales.
QXCR1000882730
On Version 2.0 and higher volume groups, if you abort the pvmove command while moving
extents belonging to a contiguous logical volume, it might leave the contiguous logical
volume with non-contiguous extents. The next time you invoke the pvmove preview option
(-p) that involves the extents of that contiguous logical volume results in incorrect output.
QXCR1000906943
When issuing the pvmove command for a physical volume that does not belong to any
volume group, the resulting error message prints the volume group name as an empty
string.
QXCR1000907287
The vgversion command incorrectly assumes that a Version 2.0 volume group can have
a minor number in the 0-511 range only. At times the command fails to convert a Version
1.0 volume group to Version 2.0 even though the number of Version 2.0 volume groups in
the system has not reached the maximum value of 512. Also, in the case of a version change
from Version 2.1 to Version 2.0, vgversion incorrectly recreates the group file and logical
volume DSFs if the minor number of the Version 2.1 volume group is greater than 511.
QXCR1000907886
Known Problems Fixed in This Version 7