HP-UX Logical Volume Manager and MirrorDisk/UX Release Notes HP-UX 11i v3 (October 2010)
Table Of Contents
- HP-UX Logical Volume Manager and MirrorDisk/UX Release Notes
- Table of Contents
- Logical Volume Manager and MirrorDisk/UX Release Notes
- About this document
- LVM and MirrorDisk/UX overview
- Known problems fixed in this version
- Known problems and limitations
- Known problems
- Auto pre-allocation occurs for all unsharing if distributed snapshot has 2 PVs
- Auto pre-allocated, distributed snapshot threshold considers all LV pre-allocated extents in PV
- Activation of Version 2.2 VG with space-efficient snapshots fails to properly mark snapshots as read-only when there are no free extents
- The lvextend command fails to increase the number of pre-allocated extents
- Limitations
- Known problems
- Installation requirements
- HP Insight Remote Support Software
- Compatibility issues
- Related documentation
- Software Availability in Native Languages

Table 1 LVM Fixes in HP-UX 11i v3 October 2010 Web Release (continued)
DescriptionDefect ID
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).
QXCR1001039721
When creating the first snapshot for a logical volume while raw I/Os are in progress, the
system panics.
QXCR1001040067
Automatic increase of pre-allocated extents does not increase by default threshold value
for striped space-efficient snapshots.
This applies only when no threshold is configured (default threshold is assumed) and only
for striped, space-efficient snapshots.
QXCR1001042095
When the LVM API lvml_session_init(), in the shared library liblvml.so, is invoked
from a threaded application, it fails with a non-zero return value.
QXCR1001043020
When attempting to halt an HP Serviceguard cluster, hosts panic with instruction TLB Fault.
During MORE operations. entries are added and deleted from the sndq linked list. Under
heavy use of MORE, it is possible for the first entry in the list to be deleted. When the cluster
is being shut down the queue is freed starting with the first entry, which has already been
freed.
QXCR1001044941
The vgcfgbackup command fails while extending a volume group with a cDSF having a
persistent DSF.
QXCR1001045693
When the server node is running nomwcsyncd, the system panics with the following
message:
"slvmp: multiple block IO requests"
QXCR1001045832
A pvcreate command on the un-partitioned device special file (DSF) incorrectly succeeds
for a disk that has a partitioned DSF already in the lvmtab file.
QXCR1001047819
The vgscan -N command fails when legacy DSF mode is disabled.
QXCR1001047826
Sometimes lvdisplay incorrectly displays the status of a snapshot logical volume as stale
even though there are no stale extents in the snapshot logical volume.
QXCR1001047828
If automatic increase of pre-allocated extents is enabled for a space-efficient, distributed
snapshot, the pre-allocated extents are increased for each unsharing IO.
QXCR1001049913
During IOs on a source logical volume, the system panics. Reboot after panic generates the
following:
lvmp_cache_scrub
QXCR1001050822
If automatic increase of pre-allocated extents is enabled for a space-efficient snapshot, a
"WARNINGS"message is logged even after the size of snapshot reaches its original logical
volume.
QXCR1001050860
When trying to add a physical volume to a shared volume group in the MORE environment
using vgextend, the command fails because the pass-through controller and the data LUN
have the same wwid.
QXCR1001053066
The vgextend command fails when trying to add a physical volume to a shared volume
group in the MORE HPVM environment.
QXCR1001063905
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.
6