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

Problem: pvdisplay -v will take a long time to complete if the physical
volume has large number of physical extents in use (about 0.5 million
extents or more).
Severity: Serious
Corrective Action: Restrict the use of the –v option when the physical volume has more
than 0.5 million physical extents in use.
Panic in lvmp_vg_lvix_to_minor(k) after removing a disk from the volume group
Defect ID: QXCR1001095451
Problem: The system panics with the following stack trace.
0xe000000000711ff0 $cold_vm_hndlr+0x750
0xe000000001dda780 bubbledown+0x0
0xe0000001c38f64b0 lvmp_vg_lvix_to_minor+0xd0
0xe0000001c38f6390 lvmp_vg_lvix_to_dev+0x50
...
This panic happens after a physical volume is removed from a volume
group and the following conditions are true:
• The physical volume had extents from a Mirrow Write Cache
(MWC) enabled mirrored logical volume.
• There were write IOs on those extents and the logical volume
was not closed properly.
This panic may happen sometime after the physical volume is
removed.
Severity: Critical
Corrective Action:
If the HP-UX 11iv3 September 2010 update or LVM October
2010 web release is installed, use pvmove to free up all the
extents on the physical volume prior to running vgreduce.
•
• Otherwise, close (and re-open) all MWC mirrored logical
volumes before invoking lvreduce.
• De-activate and activate the volume group prior to using
vgreduce.
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 9