HP-UX Logical Volume Manager and MirrorDisk/UX Release Notes (March 2010 web release)

Logical Volume Manager and MirrorDisk/UX Release Notes
About this document
LVM and MirrorDisk/UX overview
Logical Volume Manager (bundle BaseLVM) is the HP-UX default Volume Manager. It provides
the user with flexibility in configuring and managing mass storage resources. In HP-UX 11i v3,
the LVM kernel and commands are bundled with the core HP-UX product.
MirrorDisk/UX (bundle B2491BA) is an optionally purchased HP-UX product to enable LVM
mirroring functionality.
Overview of changes
The initial HP-UX 11i v3 release of LVM and MirrorDisk/UX was integrated with the new mass
storage stack, delivering significant performance, scalability, availability, and usability
enhancements. LVM was enhanced to support larger logical volumes, temporary quiescing of
volume groups, and striping with mirroring. Volume group availability was improved: resizing
a LUN and modifying volume group characteristics no longer required the volume group to be
recreated, and replacing a disk could be done online.
The March 2010 web release of LVM and MirrorDisk/UX is a defect fix only release; there are no
new features.
Known problems fixed in this version
The following table lists the known LVM and MirrorDisk/UX problems fixed in the March 2010
web release of HP-UX 11i v3.
Table 1 LVM Fixes in HP-UX 11i v3 March 2010 Web Release
DescriptionDefect ID
During a fresh installation or in cases where the /etc/lvmconf/pv_lock file has been
deleted, the following message is logged in the syslog file: /etc/lvmconf/pv_lock
file was found to be of zero size. There could be delay or failure
in the generation of unique PVIDs. This informational message has been reworded
to avoid confusion.
QXCR1000936867
In low memory conditions, the pvmove command can fail on Version 2.x volume groups
and cause subsequent Version 2.x LVM commands to hang.
QXCR1000940488
If a physical volume in a Version 2.x volume group is restored using the vgcfgrestore
command and the physical volume contains mirrored logical volumes with Mirror Write
Cache enabled (as shown by lvdisplay), user I/O to those logical volumes might
subsequently fail with EIO.
QXCR1000940892
In some instances, the pvmove command fails with the following error: pvmove: Couldn't
retrieve the allocation map of physical volume.
QXCR1000945735
For Version 2.0 and higher volume groups, if the volume group has more than 32 physical
volumes, a pvmove auto rebalance does not happen across all the physical volumes properly.
QXCR1000954120
If you use the Version 2.x volume group resizing feature (-S option) of the vgmodify
command to increase or decrease the maximum size of a 2.x volume group and then use
the vgextend command to add physical volumes to the volume group, the volume group
metadata can enter an inconsistent state such that subsequent activations of the volume
group can fail with a message similar to the following: Quorum not present, or some
physical volume(s) are missing. In addition, commands that attempt to modify
the volume group configuration can fail.
QXCR1000967236
About this document 5