HP-UX Logical Volume Manager and MirrorDisk/UX Release Notes HP-UX 11i v3 (September 2010)
Table 1 LVM Fixes in HP-UX 11i v3 September 2010 (continued)
DescriptionDefect ID
When an online vgmodify is performed on a Version 1.0 volume group that has the root
logical volume from which the system is booted, the system hangs and must be rebooted.
QXCR1001012778
In some cases, when a physical volume is removed from a volume group, the system panics.
There is no specific symptom to identify this panic. The panic occurs in the
lvmp_vg_lvix_to_minor function.
QXCR1001013882
The lvchange command does not allow changing a strict allocation policy of a striped,
mirrored logical volume to PVG-strict. The lvcreate command allows this change.
QXCR1001016043
When an MWC enabled mirrored logical volume is recovered in a volume group, if one of
the physical volumes had an I/O in its last track of a logical volume, it is wrongly identified
as corrupted; all the extents in the physical volume are marked stale.
QXCR1001017643
If either the /etc/lvmtab or /etc/lvmtab_p files are missing, the vgchgid command
might fail.
QXCR1001021755
If you execute the vgmodify command with the -E option on a Version 2.x volume group
that has a disk partition, it can fail with the metadata I/O failure error message.
QXCR1001022352
The LE on PV and PE on PV values are shown incorrectly in the distribution of logical
volume section of the lvdisplay verbose output of snapshot logical volumes.
QXCR1001028792
In some cases when performing I/O to a striped logical volume with large stripe width (>=
128), a panic occurs.
QXCR1001030574
If the volume group has a partitioned disk configured as a physical volume in the volume
group, vgversion fails.
QXCR1001030738
When a volume group is shared by HP Serviceguard cluster nodes and you issue an lvcreate
or lvremove command from the server, the command fails and a core dump is generated.
QXCR1001038146
If volume group activation fails to allocate the pre-allocated extents for a space-efficient
snapshot because there are no free extents in the volume group, the space efficient snapshot
is marked as read-only. If you attempt to increase the number of extents in the pre-allocated
pool of this space-efficient snapshot and it fails because there are no free extents in the volume
group, a panic occurs.
QXCR1001039230
After the pvmove auto rebalance command (pvmove -a VolumeGroupName) is executed
on a volume group, the first physical volume is occupied by more extents than its proportion
on the volume group. Sometimes, the first physical volume is fully occupied while other physical
volumes are having free extents.
QXCR1001039237
The vgmove command fails in a system that does not have the primary or alternate boot path
set.
QXCR1001039260
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
Auto-preallocation generates error messages in syslog
Defect ID: QXCR1001039721
Problem: In a configuration where large numbers of I/O are in progress in
many logical volumes and automatic increase of pre-allocated extents
for a space-efficient snapshot is enabled, the following message is
logged in syslog:
lvmpud->lvextend[25174]: "LogicalExtentsNumber" is not bigger than current
setting.
vmunix: LVM: ERROR: The task posted for increasing the pre-allocated extents
failed for the snapshot LV (VG 128 0x004000, LV Number: 4 8).
6 Logical Volume Manager and MirrorDisk/UX Release Notes