Veritas Volume Manager 5.1 SP1 Troubleshooting Guide (5900-1507, April 2011)

3
Use the vxsnap command to dissociate the volume from the snapshot
hierarchy:
# vxsnap [-g diskgroup] dis volume
4
Use the following command to start the volume:
# vxvol [-g diskgroup] start volume
5
Re-run the failed reattach or refresh command.
This results in a full resynchronization of the volume. Alternatively, remove
the snapshot volume and recreate it if required.
Recovering from 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.
To recover from copy-on-write failure
1
Use 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
3
Prepare the volume using the following command:
# vxsnap [-g diskgroup] prepare volume [ndcomirs=number] \
[regionsize=size] [drl=yes|no|sequential] \
[storage_attribute ...]
The volume can now be used again for snapshot operations.
Alternatively, you can remove the snapshot volume and recreate it if required.
39Recovering from instant snapshot failure
Recovering from copy-on-write failure