Veritas Volume Manager 4.1 Troubleshooting Guide (HP-UX 11i v3, February 2007)

Copy-on-write Failure
28 VERITAS Volume Manager Troubleshooting Guide
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:
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 ...]
See the VERITAS Volume Manager Administrator’s Guide and the vxsnap(1M) manual
page for full details of how to use the vxsnap prepare command.
The volume can now be used again for snapshot operations.
Alternatively, you can remove the snapshot volume and recreate it if required.