Veritas Volume Manager 4.1 Release Notes (5900-0590, March 2010)

If it is an absolute must that a disk group not be auto-imported when the system is rebooted,
the disk group should be imported temporarily using the -t flag of the vxdg import
command.
• Volumes Not Started Following a Reboot
Problem
During fast system reboots, on a system with many volumes, vxconfigd may not be able
to auto-import all of the disk groups by the time vxrecover -s is run to start the volumes.
As a result, some volumes may not be started when an application starts after reboot.
Workaround
Check the state of the volumes before starting the application, or execute the sleep command
(sleep <sec>) before the last invocation of vxrecover.
• Volumes Not Started After Disk or I/O Failure
Problem
The vxrecover command starts a volume only if it has at least one plex that is in the ACTIVE
or CLEAN state and is not marked STALE, IOFAIL, REMOVED, or NODAREC. If such a plex is
not found, VxVM assumes that the volume no longer contains valid up-to-date data, and
therefore the volume is not started automatically. A plex can be marked STALE or IOFAIL
as a result of a disk failure or an I/O failure.
Workaround
In such cases, to forcefully start the volume, use the following command:
# vxvol -f start volume
However, you must first determine the cause of the problem before you run this command.
The volume may need to be restored from backup, or the disk may need to be replaced.
• Multipathing status reported by the vxdmpadm command maybe incorrect
On an HP-UX 11i v3 operating system, the VxVM 4.1 DMP depends on the information
provided by the HP native multipathing driver. VxVM 4.1 does not have direct access to
multiple paths of a device. Therefore, VxVM 4.1 may not report the correct status as it only
returns the status reported by the HP native multipathing driver.
Documentation Errata
The following is a list of content in the documentation included with the Veritas 4.1 suite of
products on the HP-UX 11i v3 that the readers must ignore:
Title: Veritas Volume Manager 4.1 Administrator's Guide
1. Chapter 3: Administering DMP: VxVM DMP is in bypass mode on HP-UX 11i v3. For more
information see "Veritas 4.1 Installation Guide" available at http://docs.hp.com.
2. Chapter 11: Configuring Off-Host Processing: FastResync is not supported with VxVM 4.1
on HP-UX 11i v3. Page 49, 50, 51: Content on FastResync must be ignored.
3. Chapter 13: Administering Cluster Functionality: Cluster Functionality is not supported
with VxVM 4.1 on HP-UX 11i v3. All content related to the clusters must be ignored.
4. Cross Platform Data sharing is not supported with VxVM 4.1. All content mentioning CDS
needs must be ignored.
5. SAM is deprecated in HP-UX 11i v3 and replaced by System Management Home Page
(SMH). All content that mention SAM must be ignored.
6. All content on DMP and DMP tunable parameters mentioned in the document must be
ignored.
18 Veritas Volume Manager 4.1 Release Notes