Veritas Volume Manager 5.0.1 Troubleshooting Guide, HP-UX 11i v3, First Edition, November 2009

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.
Recovering from I/O errors during resynchronization
Snapshot resynchronization (started by vxsnap syncstart, or by specifying
sync=on to vxsnap) stops if an I/O error occurs, and displays the following message
on the system console:
VxVM vxsnap ERROR V-5-1-6840 Synchronization of the volume
volume stopped due to I/O error
After correcting the source of the error, restart the resynchronization operation.
To recover from I/O errors during resynchronization
◆
Type the following command:
# vxsnap [-b] [-g diskgroup] syncstart volume
39Recovering from instant snapshot failure
Recovering from copy-on-write failure