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

Table 1 LVM Fixes in HP-UX 11i v3 April 2011 Web Release
DescriptionDefect ID
pvdisplay -v takes a long time to complete if the physical volume has large number of
physical extents in use (about 0.5 million extents or more).
QXCR1001080067
vgchange -a y reports activation mode conflict failure with the following error message
when the previous vgchange -c reported success even though internally it did not change
the mode correctly.
$vgchange -a y vgname
vgchange: Activation mode requested for the volume group <vgname> conflicts with configured
mode.
QXCR1001086866
System panics after a physical volume is removed from a volume group when both of the
following conditions are true:
• The removed physical volume has extents allocated for a mirrored logical volume with
MWC (mirror write cache) enabled.
• There were write IOs on these extents and the logical volume was not closed properly.
The stack trace of the panic will look like below:
0xe000000000711ff0 $cold_vm_hndlr+0x750
0xe000000001dda780 bubbledown+0x0
0xe0000001c38f64b0 lvmp_vg_lvix_to_minor+0xd0
0xe0000001c38f6390 lvmp_vg_lvix_to_dev+0x50
QXCR1001095451
In a LVM shared volume group, if both internal resync (triggered by a physical volume
coming back online) and I/Os are targeted for the same extents (in any of the nodes), it may
lead to IOs hang when there is heavy I/O load and frequent intermittent disk failures.
QXCR1001110492
The lvcreate command allocates one extent in the physical volume group which has one
physical volume and the remaining extents in the next physical volume group when the logical
volume has distributed pvg-strict policy.
QXCR1001101479
The lvextend command allocates one extent in the physical volume group which has one
physical volume and the remaining extents in the next physical volume group when the logical
volume has distributed pvg-strict policy.
QXCR1001110394
Known problems and limitations
This section provides a list of known problems and limitations as known to HP at time of publication.
If workarounds are available, they are included.
Known problems
In Shared LVM, client panics after joining the Serviceguard cluster
Defect ID: QXCR1001091075
Problem: In a Serviceguard cluster environment, one of the client panics with
the following stack trace.
0xe00000012f219ca0 slvmp_process_bad_reply+0x320
0xe000000000ed4490 invoke_callouts_for_self+0x460
0xe000000000ec6bf0 soft_intr_handler+0x1c0
Severity: Critical
Corrective Action: Currently, none.
Known problems and limitations 5