VERITAS Volume Manager 3.5 Release Notes (August 2003)

VERITAS Volume Manager™ HP-UX 11i v2 Release Notes
Patches and Fixes in This Version
Chapter 1 43
Stopping and Starting Layered Volumes If a layered volume is in
use when a vxvol stopall command is issued, then only the sub-volumes
are disabled. The layered volume remains enabled.
When a vxvol stop layered-volume command is issued, then only the top
layered volume is stopped. The sub-volumes remain enabled.
When a vxvol start layered-volume command is issued, then only the top
layered volume is started. The sub-volumes remain disabled.
Adding Swap Space Using VxVM Volumes The HP System
Administration Manager (SAM) currently does not have the capability to
add swap space using VxVM volumes. Please refer to the VERITAS
Volume Manager Installation Guide for more information and
workarounds for this problem.
Using SAM to Launch the VEA Client
• Problem: It is currently not possible to launch the VEA client from
SAM.
• Workaround: Until a patch to overcome this problem becomes
available, you should use the CLI to launch VEA. Please continue to
check the HP patch web site for future availability of this patch.
Enclosure-based Naming on Persistent Simple or Nopriv Disks
For users withpersistent simple or nopriv disks,enclosure-based naming
can cause errors in two situations:
Step 1. See “After Upgrading to VxVM 3.5” on page 44.
Step 2. See “After Changing Your Disk Naming Scheme” on page 44.
NOTE For more information, refer to “Issues Regarding
Persistent Simple/Nopriv Disks with Enclosure-Based
Naming” in the VERITAS Volume Manager
Administrator’s Guide. See also vxdarestore (1M) manual
page.