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

Known Problems Fixed in This Version
The following table lists the known LVM and MirrorDisk/UX problems fixed in the March 2009
release of HP-UX 11i v3.
Table 1 LVM Fixes in HP-UX 11i v3 March 2009
DescriptionDefect ID
In all localized utf8 locales, all LVM display commands produce output with corrupted
characters, truncations, and misalignment.
QXCR1000824861
When a volume group (VG) is in a deactivated state, if you issue the vgchange -a n
command, the system returns the strerror message.
QXCR1000827038
In an HP Serviceguard cluster, a system can panic during the recovery of a server for a 2.x
volume group, if a physical volume is unavailable.
QXCR1000843064
If a VG with a logical volume (LV) that has Mirror Write Cache (MWC) enabled is activated
after a system failure, the activation can hang.
QXCR1000843538
In an HP Serviceguard cluster, a system can panic when quiescing a shared version 2.0
volume group.
QXCR1000848376
In an HP Serviceguard cluster, a System can panic after cross activation and adding mirror
to LV.
QXCR1000850334
During volume group activation of a volume group containing logical volumes that do not
have MWC enabled, if an LV was not closed properly during previous deactivation, LVM
marks all the extents stale except one. Currently, LVM is picking the first available fresh
copy, but few times it is picked from the unavailable physical volume (PV).
QXCR1000854405
In an HP Serviceguard cluster, deactivation can fail on some nodes of a cluster if a server
has failed.
QXCR1000865844
The vgimport command fails to verify the unique LVM disk ID on HP-UX 11i v3.
QXCR1000870963
The system panics during a DLKM unload of the lvmp module because of a race condition.
QXCR1000874763
On systems without an /etc/lvmtab_p file, unloading the lvmp module can generate
extraneous vgdisplay messages.
QXCR1000878178
Using LVM 2.0 and higher volumes with physical volumes (PV) groups that have physical
extents (PEs) greater than 65535 can cause data corruption. Issuing lvsync and vgsync
commands marks the extents as current, but after an activation cycle, the extents are stale.
QXCR1000887104
Known Problems Fixed in This Version 7