Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

33Recovery from failure of instant snapshot operations
Failure of vxsnap restore
If the vxsnap make operation was being performed on a prepared cache object by
specifying the cache attribute, the cache object remains intact after deleting the snapshot.
If the cachesize attribute was used to specify a new cache object, the cache object does
not exist after deleting the snapshot.
Failure of vxsnap restore
If a vxsnap restore operation fails, the volume being restored may go into the
DISABLED state. Use the following command to start the volume:
# vxvol [-g diskgroup] start volume
Failure of vxsnap reattach or refresh
If a vxsnap reattach or refresh operation fails, the volume being refreshed may go into
the DISABLED state, be marked invalid and be rendered unstartable. You can use the
following command to check that the inst_invalid flag is set to on:
# vxprint [-g diskgroup] -F%inst_invalid volume
Use the following steps to recover the volume:
1Use the
vxmend command to clear the volume’s tutil0 field:
# vxmend [-g diskgroup] clear tutil0 volume
2Use the vxsnap command to dissociate the volume from the snapshot hierarchy:
# vxsnap [-g diskgroup] dis volume
3 Use the following command to start the volume:
# vxvol [-g diskgroup] start volume
4 Re-run the failed reattach or refresh command.
Note: This results in a full resynchronization of the volume. Alternatively, remove
the snapshot volume and recreate it if required.
Copy-on-write failure
If an error is encountered while performing an internal resynchronization of a volume’s
snapshot, the snapshot volume goes into the INVALID state, and is made inaccessible for
I/O and instant snapshot operations.
Use the following steps to recover the snapshot volume:
1Use the
vxsnap command to dissociate the volume from the snapshot hierarchy:
# vxsnap [-g diskgroup] dis snapshot_volume
2 Unprepare the volume using the following command:
# vxsnap [-g diskgroup] unprepare snapshot_volume