Veritas InfoScale™ 7.3.1 Troubleshooting Guide - Solaris
- Introduction
- Section I. Troubleshooting Veritas File System
- Section II. Troubleshooting Veritas Volume Manager
- Recovering from hardware failure
- Failures on RAID-5 volumes
- Recovery from failure of a DCO volume
- Recovering from instant snapshot failure
- Recovering from failed vxresize operation
- Recovering from boot disk failure
- Hot-relocation and boot disk failure
- Recovery from boot failure
- Repair of root or /usr file systems on mirrored volumes
- Replacement of boot disks
- Recovery by reinstallation
- Managing commands, tasks, and transactions
- Backing up and restoring disk group configurations
- Troubleshooting issues with importing disk groups
- Recovering from CDS errors
- Logging and error messages
- Troubleshooting Veritas Volume Replicator
- Recovery from configuration errors
- Errors during an RLINK attach
- Errors during modification of an RVG
- Recovery on the Primary or Secondary
- Recovering from Primary data volume error
- Primary SRL volume error cleanup and restart
- Primary SRL header error cleanup and recovery
- Secondary data volume error cleanup and recovery
- Troubleshooting issues in cloud deployments
- Recovering from hardware failure
- Section III. Troubleshooting Dynamic Multi-Pathing
- Section IV. Troubleshooting Storage Foundation Cluster File System High Availability
- Troubleshooting Storage Foundation Cluster File System High Availability
- Troubleshooting CFS
- Troubleshooting fenced configurations
- Troubleshooting Cluster Volume Manager in Veritas InfoScale products clusters
- Troubleshooting Storage Foundation Cluster File System High Availability
- Section V. Troubleshooting Cluster Server
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting I/O fencing
- System panics to prevent potential data corruption
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the Veritas InfoScale products cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- VCS message logging
- Troubleshooting and recovery for VCS
- Section VI. Troubleshooting SFDB
Recovering a version 0 DCO volume
To recover a version 0 DCO volume
- Correct the problem that caused the I/O failure.
- Use the following command to remove the badlog flag from the DCO:
# vxdco [-g diskgroup] -o force enable dco_name
For the example output, the command would take this form:
# vxdco -g mydg -o force enable vol1_dco
The entry for vol1_dco in the output from vxprint now looks like this:
dc vol1_dco vol1 - - - -
- Restart the DCO volume using the following command:
# vxvol [-g diskgroup] start dco_log_vol
For the example output, the command would take this form:
# vxvol -g mydg start vol1_dcl
- Use the vxassist snapclear command to clear the FastResync maps for the original volume and for all its snapshots. This ensures that potentially stale FastResync maps are not used when the snapshots are snapped back (a full resynchronization is performed). FastResync tracking is re-enabled for any subsequent snapshots of the volume.
Warning:
You must use the vxassist snapclear command on all the snapshots of the volume after removing the badlog flag from the DCO. Otherwise, data may be lost or corrupted when the snapshots are snapped back.
If a volume and its snapshot volume are in the same disk group, the following command clears the FastResync maps for both volumes:
# vxassist [-g diskgroup] snapclear volume \ snap_obj_to_snapshot
Here snap_obj_to_snapshot is the name of the snap object that is associated with volume that points to the snapshot volume.
For the example output, the command would take this form:
# vxassist -g mydg snapclear vol1 SNAP-vol1_snp
If a snapshot volume and the original volume are in different disk groups, you must perform a separate snapclear operation on each volume:
# vxassist -g diskgroup1 snapclear volume snap_obj_to_snapshot # vxassist -g diskgroup2 snapclear snapvol snap_obj_to_volume
Here snap_obj_to_volume is the name of the snap object that is associated with the snapshot volume, snapvol, that points to the original volume.
For the example output, the commands would take this form if SNAP-vol1 had been moved to the disk group, snapdg:
# vxassist -g mydg snapclear vol1 SNAP-vol1_snp # vxassist -g snapdg snapclear SNAP-vol1 vol1_snp
- To snap back the snapshot volume on which you performed a snapclear, use the following command (after using the vxdg move command to move the snapshot plex back to the original disk group, if necessary):
# vxplex -f [-g diskgroup] snapback volume snapvol_plex
For the example output, the command would take this form:
# vxplex -f -g mydg snapback vol1 vol1-03
You cannot use the vxassist snapback command because the snapclear operation removes the snapshot association information.