Unable to start snap volume ERROR V-5-1-11802 because inst_invalid attribute is set

book

Article ID: 100023467

calendar_today

Updated On:

Description

Error Message

 # vxvol -g abcdg -f start SNAP_vol76
VxVM vxvol ERROR V-5-1-11802 Volume SNAP_vol76 cannot be started 

# vxprint -g abcdg -m | egrep '^vol|inst_invalid'
vol  SNAP_vol76
        inst_invalid=on               <<<  Inst_invalid attribute is set
vol  SNAP_vol112
        inst_invalid=on
vol  SNAP_vol113
        inst_invalid=on
.....

Cause

Once the snapshot volume is marked invalid, VxVM will not start them because the data in the volume is considered as invalid.
 

Resolution

There are only two ways to start the snapshot.

1. Try to run ‘vxsnap refresh’ again to refresh the snapshot volume and see if the snapshot volume will become valid again.  The exiting data in the snapshot volumes will be replaced with latest data from source volume.

# vxsnap -g  refresh

 

2. Dissociate the snapshots and start them, but the customer will need to do the full resync again if snapshot needs to be taken again.

 

# vxmend -g -r clear all  
 

# vxsnap -g dis  
 
Note - use force -f option if needed
 
# vxvol -g start     
 
Note - use force -f option if needed
 
# vxprint -qhtg  
 
Note - Verify volume started 

After the snapshot volume is started, please verify the data and see if the data is intact. During the previous failed snapshot operation, the data may be affected.   After the data is verified, we can continue working with volume or run backups.

When a snapshot needs to be taken again, a full resynchronization will be required.
# vxsnap -g make source=/snap=/sync=no  
# vxsnap -bg  syncstart

Applies To

Veritas Volume Manager (VxVM) with snapshot volumes on all platforms

Issue/Introduction

During vxsnap creation or refresh, if involved volumes are busy and diskgroup is deported, the vxsnap creation or refresh could fail and causes the snapshot volume to be marked invalid (inst_invalid=on)