 | ||
| Recovering from the failure of vxsnap make for space-optimized instant snapshots | ||
|---|---|---|
| Prev | Recovering from instant snapshot failure | Next |
| ||
| Recovering from the failure of vxsnap make for space-optimized instant snapshots | ||
|---|---|---|
| Prev | Recovering from instant snapshot failure | Next |
If a vxsnap make operation fails during the creation of a space-optimized instant snapshot, the snapshot volume may go into the INSTSNAPTMP state. VxVM can usually recover the snapshot volume without intervention. However, in certain situations, this recovery may not succeed. If the recovery does not succeed, the snapshot volume must be deleted.
To recover from the failure of the vxsnap make command for space-optimized instant snapshots
# vxedit [-g diskgroup] -r -f rm snapshot_volume
Be sure to specify the -r (recursive) option and the -f (force) option because the volume is enabled and has plexes and logs attached to it.
Alternatively, the snapshot volume is removed automatically when the system is next restarted.
If the vxsnap make operation was being performed on a prepared cache object by specifying the cache attribute, the cache object remains intact after you delete the snapshot. If the cachesize attribute was used to specify a new cache object, the cache object does not exist after you delete the snapshot.
# vxmend [-g diskgroup] clear tutil0 original_volume