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 from a failed vxresize shrink operation
The vxresize command operates on both the file system and the underlying volume. For a shrink operation, the vxresize command calls the fsadm command to resize the file system and then calls the vxassist command to resize the underlying volume. In some cases, the file system shrink operation succeeds but the volume shrink operation fails. This situation may occur if you specify an invalid medianame operand to the vxresize command. A medianame operand may be invalid if the disk does not exist or if the disk is not in the specified disk group. The vxresize command passes the invalid parameter to the vxassist volume resize operation, which then fails. A message is displayed similar to the following:
VxVM vxassist ERROR V-5-1-18606 No disks match specification for Class: dm, Instance: vmr720-10_disk_14 VxVM vxresize ERROR V-5-1-4703 Problem running vxassist command for volume vol1, in diskgroup testdg
The operation results in a reduced file system size, but does not change the volume size. This behavior is expected; however, you need to correct the volume size to match the file system size.
Workaround:
Repeat the vxresize command with the required size but without any disk parameters. The file system is not resized again when the current file system size and new file system size are the same. The vxresize command then calls the vxassist command, which reduces the volume size. The file system size and the volume sizes are now the same.