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

Table 1 LVM Fixes in HP-UX 11i v3 March 2012 Release (continued)
DescriptionDefect ID
Resolution details: vgversion has been enhanced so that the cluster lock can be removed
by running vgchgid first and then subsequently running vgversion to upgrade the volume
group.
In a 3 node cluster, the deactivation of a shared volume group in the server fails if any server
crash occurred earlier followed by a deactivation of a volume group on the other client.
QXCR1001145030
In a 2 node cluster, if any server crash occurred during deactivation of the shared volume
group in the server node, subsequent vgdisplay on the client node hangs.
QXCR1001145047
Activation of shared volume group on the second node hangs forever when the activation
command is issued while the server has crashed.
QXCR1001145096
In a 4 node cluster, during heavy IO load to one or more mirrored logical volumes and with
intermittent disk failures, one of the client panics with the following stack trace:
QXCR1001152106
panic+O4410
lvmp:slvmp_dequeue_done_requests+0x1a0
lvmp:slvmp_process_commit_msg+0x160
lvmp:slvmp_commit_msg_hdlr+0x210
lvmp:lvmp_kd_daemon+0x1b0
lvmp:lvmp_kd_fork1+0x210
lvmp:lvmp_kd_fork+0x90
lvmp:lvmp_kd_init+0x1a0
lvmp:lvmp_init+0x880
lvmp:lvmp_load+0x90
mod_load_helper+0x2a0
modld+0x2d0
kc_dispatch_helper+0x9a0
kc_dispatch+0x550
gio_install_drivers+0x50
io_virt_mode_config
Known issues and limitations
This section provides a list of known issues and limitations as known to HP at time of publication.
If workarounds are available, they are included.
Known issues
2.x VG fails to activate with “On disk LVM metatdata structures are corrupted” error message
Defect ID: QXCR1001182973
Problem: Volume groups that were migrated from 1.0 to 2.X using a version
of vgversion prior to the August 2011 web release or using the
September 2011 release may fail to activate, resulting with the error
message: “On disk LVM metadata structures are
corrupted”.
Severity: Serious
Corrective Action: To fix this problem, restore the volume group back to its 1.0 version
configuration using the vgcfgrestore command, and then migrate
to 2.x using the new enhanced vgversion command, first made
available in the August 2011 web release (after September 2011
release) and also provided in the March 2012 release.
Memory leaks in LVM when using shared volume group
Defect ID: QXCR1001178600
Problem: If a cluster is stopped and restarted, available memory is reduced
approximately by 512KB due to LVM memory leaks.
6 Logical Volume Manager and MirrorDisk/UX Release Notes