VERITAS Volume Manager 3.5 Release Notes (August 2002)

Chapter 1

VERITAS Volume Manager™ Release Notes

Patches and Fixes in This Version

to execute a default snapback operation (resynchronizing from the original volume), and the system crashes while the

operation is still in progress, you will ﬁnd, when the system comes back up and the volumes are restarted, that the

snapshot plexes are not associated with any volume.

• Workaround: To recover from this situation, you should use the following procedure:

Step 1. Use the following commands to discover the original volume name of each snapshot plex:

# volrid=‘vxprint -g diskgroup -p -F “%snap_rid” plexname‘

# vxprint -g diskgroup -n -v -e v_rid=$volrid

Step 2. Using the information discovered in the previous step, identify the volumes to which the snapshot plexes

originally belonged, and reattach them to those original volume as in the following command:

# vxplex att original_volume plex1 [plex2 ...]

Crash Recovery after using vxassist -o resyncfromreplica snapback snapvol

• Problem: When you use the following command:

# vxassist -o resyncfromreplica snapback snapvol

to execute a snapback operation (resynchronizing from the replica volume), and the system crashes while the

operation is still in progress, you will ﬁnd, when the system comes back up, that the original volume fails with the

following error message:

vxvm:vxvol: ERROR: Volume original_volume has no CLEAN or \ non-volatile ACTIVE plexes

• Workaround: To correct this situation, you should use the following procedure:

Step 1. Disassociate all STALE plexes from the original volume:

# vxplex dis staleplex1 [staleplex2 ...]

Step 2. Convert all SNAPTMP plexes in the original volume to ACTIVE:

# vxplex convert state=ACTIVE tmpplex1 [tmpplex2 ...]

Step 3. Restart the original volume:

# vxvol start original_volume

Step 4. Reattach the plexes that you disassociated in step 1:

# vxplex att original_volume staleplex1 [staleplex2 ...]

This procedure results in a full synchronization of these plexes from the original volume.

VEA Issues

The following issues have been identiﬁed as VEA problems, and will be ﬁxed in either patches or a future

release of VxVM.

Connecting to X Windows The following X Window System error may occur when starting VEA:

Xlib: connection to "hostname:0.0" refused by server

Xlib: Client is not authorized to connect to Server

Workaround: Allow X server access by typing:

xhost + [hostname]

Volume Manager and Multi-Host Failover Conﬁgurations Outside the context of clustering

functionality, Volume Manager disk groups can be imported (made available) from only one host at any given

time. When a host imports a disk group as private, the volumes and conﬁguration of that disk group becomes