HP-UX Logical Volume Manager and MirrorDisk/UX Release Notes HP-UX 11i v3 March 2010 Web Release (B.11.
© Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents Logical Volume Manager and MirrorDisk/UX Release Notes......................................5 About this document..............................................................................................................................5 LVM and MirrorDisk/UX overview........................................................................................................5 Overview of changes..................................................................................................
List of Tables 1 4 LVM Fixes in HP-UX 11i v3 March 2010 Web Release....................................................................
Logical Volume Manager and MirrorDisk/UX Release Notes About this document LVM and MirrorDisk/UX overview Logical Volume Manager (bundle BaseLVM) is the HP-UX default Volume Manager. It provides the user with flexibility in configuring and managing mass storage resources. In HP-UX 11i v3, the LVM kernel and commands are bundled with the core HP-UX product. MirrorDisk/UX (bundle B2491BA) is an optionally purchased HP-UX product to enable LVM mirroring functionality.
Table 1 LVM Fixes in HP-UX 11i v3 March 2010 Web Release (continued) Defect ID Description QXCR1000969018 Booting a volume group using maintenance mode boot can result in the corruption of the root file system. The symptom is an error message to the system console on the next boot similar to the following: fsadm: ERROR: V-3-20295: device record checksum is invalid. QXCR1000974930 For Version 2.
pvmove displays an incorrect message related to an alternate link Defect ID: QXCR1000998563 Problem: If you invoke pvmove and specify both the primary link and alternate link of the physical volume, an incorrect message about the alternate link is displayed. Severity: Medium Corrective Action: None. Only the message is incorrect.
• • pre-allocated pool and lead to the snapshot and its predecessors being marked as inoperative. At this point, you must increase the pre-allocated extent pool size for the snapshot logical volume. Under very low memory conditions, the removal of a single snapshot using lvremove can hang if data unsharing is required. For more limitations on snapshots, see the Using LVM Logical Volume Snapshots white paper. Installation requirements This section describes the installation requirements for this release.
disks must install the HP Serviceguard September 2008 patch. For more information, see the HP Serviceguard Version A.11.18 Release Notes. VxVM 4.1 commands Several VxVM 4.1 commands check whether a specified disk device is being used by LVM before overwriting it. For these commands to correctly check whether a device is part of a Version 2.
HP recommends converting volume groups with multipathed disks to persistent device special files and using native multipathing, as described in the migration white paper in “Related documentation”. However, if you want backward-compatible PVLink behavior, you must use legacy device special files for physical volumes, and disable the mass storage stack multipathing for those physical volumes.
Sharing volume groups in an HP Serviceguard cluster To share a volume group in an HP Serviceguard cluster where the cluster nodes have different versions of the LVM product installed, use the following guidelines: • • • To share a version 2.1 volume group, you must install the HP-UX 11i v3 September 2008 release or above on all the cluster nodes. To share a 2.2 volume group, you must install the HP-UX 11i v3 March 2010 release or above on all the cluster nodes.
