HP-UX Logical Volume Manager and MirrorDisk/UX Release Notes (5900-2442, August 2012)

vgmodify -a -S modifies a subset of the PVs
Defect ID: QXCR1001211881
Problem: Under certain conditions a subset of the PV’s in the vg are changed
in size by vgmodify but this has no advantage and leaves the vg
susceptible to further problems.
Severity: Serious
Corrective Action: If the failure occurred on a PV due to lack of free PEs, then use
pvmove as suggested in the output of vgmodify to free up extents
and retry the vgmodify operation.
To prevent this condition from occurring, use the preview mode of
vgmodify (–r option) to make sure the modification is possible.
vgimport 2.X fails saying a PV doesn't belong to the same VG
Defect ID: QXCR1001222652
Problem: Under rare conditions, vgimport fails with following failure message
because of a metadata ID mismatch.
vgimport vg22 /dev/dsk/vrd05[01]p00
vgimport: The Physical Volumes specified on the command line do
not belong to the same Volume Group
Severity: Serious
Corrective Action: Run vgchgid on all the PVs in the VG. vgchgid will change the VGID
on all copies.
vgchange returns non-zero with option -c n –S n
Defect ID: QXCR1001217016
Problem: vgchange –c n –S n <vgname> would return non-zero value in a
non-clustered system.
Severity: Serious
Corrective Action: Skip –S n since it is implicit when –c n is specified. Just use vgchange
–c n.
VG Quiesce on shared vg hangs while resync is going on
Defect ID: QXCR1001154451
Problem: In a cluster with 3 or more nodes, suspending the VG (vgchange –Q)
on the first client node hangs if resync is in progress for that VG and
also the server of the VG crashes at the same time.
Severity: Serious
Corrective Action: None.
Limitations
This section provides a list of limitations as known to HP at time of publication.
• Logical volumes that have snapshots associated with them might experience an increase in
latencies associated with writes. This is also applicable for writes on (writable) snapshots
themselves.
• With the HP-UX 11i v3 September 2010 Update release, when the number of extents remaining
in a space-efficient snapshot logical volume’s pre-allocated pool falls beyond a certain internally
computed threshold, by default, LVM tries to increase the pre-allocated pool size by threshold
Known issues and limitations 7