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

Table 1 LVM Fixes in HP-UX 11i v3 March 2011 Release (continued)
DescriptionDefect ID
Resync of stale extents on a striped and mirrored snapshot logical volume fails with 'I/O
error'. This behavior is seen only on HP-UX 11iv3 September 2010 updates and onwards.
QXCR1001065169
In PA RISC systems, vgdisplay core dumps while any volume group is quiesced and when
the LANG variable is set to 'C' Locale.
QXCR1001066034
lvdisplay of the original logical volume does not list the device special file (DSF) entries
corresponding to snapshots of the logical volume under the ‘Associated snapshots’
field, if the DSF of the snapshots does not exist.
QXCR1001067093
On a shared Version 2.1 or above volume group, any configuration change may hang while
a background resync operation, if any, is in progress. This background resync might be
performed by a nomwcsyncd user space daemon or triggered when a offline physical volumes
comes back online. Note that the hang does not occur for resync's in progress that are started
through LVM commands.
QXCR1001067496
The pvdisplay command displays the number of logical extents of the original logical
volume as the number of logical extents of a space-efficient snapshot logical volume.
QXCR1001067665
An attempt to perform pvmove auto-rebalance of the entire volume group may hang when
resynchronization of a logical volume of a Version 2.2 volume group is in progress and the
volume group has snapshots configured.
QXCR1001069284
In the Shared LVM environment, the client panics with the panic string:
slvmp_update_vgsa_mem_copy: unknown type
and with the following Stack Trace:
0xe00000012e9fae80 slvmp_update_vgsa_mem_copy+0x880
0xe00000012e9f99d0 slvmp_update_sa_state+0x220
0xe00000012e9f2860 slvmp_process_intent_msg+0xa0
0xe00000012e9f2e40 slvmp_intent_msg_hdlr+0x1e0
QXCR1001071222
When the activation of a Version 2.2 volume group with space-efficient snapshots fails to
allocate pre-allocated extents due to lack of free extents, the vgchange command should
mark the snapshots (with read/write permission) as read-only to prevent the snapshots from
becoming over-committed and inoperative. Instead, the vgchange command displays
“Invalid argument” and fails to mark the space-efficient snapshot logical volumes as
read-only.
QXCR1001071538
After a system crash, activation of a Version 2.x volume group will hang when all of the
following conditions are true:
• More than one of its logical volumes are configured with mirrors.
• One of its mirrored logical volumes' mirror consistency recovery policy was earlier changed
from Mirror Write Cache (MWC) to NOMWC (see lvchange(1M)).
• Prior to the system crash, there were in-flight I/Os to the logical volume whose consistency
was changed earlier and the physical volumes mapped to this logical volume are currently
not attached.
QXCR1001071925
When the number of pre-allocated extents of a space-efficient snapshot is zero, in other words,
'Current pre-allocated LE' displayed by the lvdisplay command is zero, an
attempt to increase the number of pre-allocated extents using the lvextend command fails
even though there are enough free extents in the volume group to satisfy the allocation policy
of the snapshot.
QXCR1001077247
In Shared LVM environment, when a physical volume, which is configured with more than
one path, is removed by specifying all paths in a single vgreduce command from a Version
2.2 volume group, the client’s /etc/lvmtab_p is not updated, causing inconsistency between
the server and client configuration. Any volume group related activities would report error
about this inconsistency.
QXCR1001077256
In lvdisplay verbose output of a mirrored space-efficient snapshot logical volume, the
mapping of the fourth physical extent allocated to a logical extent is displayed incorrectly for
pre-allocated extents.
QXCR1001077261
Known problems fixed in this version 7