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

Logical Volume Manager and MirrorDisk/UX Release Notes
About this document
This document provides information about the Logical Volume Manager (LVM) and
MirrorDisk/UX products in the October 2010 web release of HP-UX 11i v3.
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 October 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 October 2010
web release of HP-UX 11i v3.
Table 1 LVM Fixes in HP-UX 11i v3 October 2010 Web Release
DescriptionDefect ID
If the lvmtab file is missing, a pvcreate on the un-partitioned device special file (DSF)
incorreclty succeeds for a disk that has a partitioned DSF as a member of the root volume
group.
QXCR1000963987
When creation of snapshot is performed on a version 1.0 volume group, the command
returns the following incorrect error messages:
Volume group VGname does not exist in the /etc/lvmtab file. Volume
group VGname does not exist in the /etc/lvmtab_p file.
QXCR1001026821
When activating a volume group with snapshots, the system panics. In some cases, the
deletion of space-efficient snapshot logical volumes causes a panic. This can happen after
an attempt to increase the size of a logical volume that has snapshots associated with it. The
lvextend command might fail because no free extents are available in the volume group.
If you create a new snapshot or issue write I/Os that cause data unsharing on the logical
volume's space-efficient snapshot, and then try to delete some space-efficient snapshot
logical volumes, the system panics. Subsequent activation of the volume group might also
panic.
QXCR1001030741
About this document 5