VERITAS Volume Manager 3.5 Release Notes (August 2002)

Chapter 1

VERITAS Volume Manager™ Release Notes

Patches and Fixes in This Version

• Workaround: If the system reboots before the grow or shrink of a layered volume completes, the volume is

left with an intermediate layout. In this case, the user has to use vxassist convert to restore the volume to

its original layout.

After a layered volume is resized, the volume names, the plex names and the subdisk names associated

with the subvolumes, are changed.

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 with persistent simple or

nopriv disks, enclosure-based naming can cause errors in two situations:

Step 1. See “After Upgrading to VxVM 3.5” on page 30.

Step 2. See “After Changing Your Disk Naming Scheme” on page 30.

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.

After Upgrading to VxVM 3.5

If you upgrade your system to Volume Manager 3.5 and you have persistent simple or nopriv disks and you

select to change from c#t#d# naming to enclosure-based naming, these disks may be in an error state after

upgrading. To recover these disks, run vxdarestore after you have completed the upgrade.

After Changing Your Disk Naming Scheme

If you change your Volume Manager 3.5 system to enclosure-based naming using vxdiskadm, you need to

check any persistent simple or nopriv disks, as these disks may be in an error state after the change. To

recover these disks, run vxdarestore.