T3 recovery completed with errors: One or more of the volumes are offline
because there was fast write data in the cache. To bring the volumes online, see
“Recovering from offline volumes using the CLI” for details.
v T3 failed
Call the support center. Do not attempt any further action.
Verify that the environment is operational by completing the checks that are
provided in “What to check after running the system recovery” on page 387.
If any errors are logged in the error log after the system recovery procedure
completes, use the fix procedures to resolve these errors, especially the errors that
are related to offline arrays.
If the recovery completes with offline volumes, go to “Recovering from offline
volumes using the CLI.”
After you complete the storage system recovery procedure, contact support for
assistance with recovering the file modules, so access to the file systems can be
restored.
Recovering from offline volumes using the CLI
If a Tier 3 recovery procedure completes with offline volumes, then it is likely that
the data which was in the write-cache of the node canisters was lost during the
failure that caused all of the node canisters to lose the block storage system cluster
state. You can use the command-line interface (CLI) to acknowledge that there was
lost data lost from the write-cache, and bring the volume back online to attempt to
deal with the data loss.
About this task
If you have run the recovery procedure but there are offline volumes, you can
complete the following steps to bring the volumes back online. Any volumes that
are offline and are not thin-provisioned (or compressed) volumes are offline
because of the loss of write-cache data during the event that led all node canisters
to lose their cluster state. Any data lost from the write-cache cannot be recovered.
These volumes might need additional recovery steps after the volume is brought
back online.
Note: If you encounter errors in the error log after running the recovery procedure
that are related to offline arrays, use the fix procedures to resolve the offline array
errors before fixing the offline volume errors.
Example
Complete the following steps to recover an offline volume after the recovery
procedure has completed:
1. Delete all IBM FlashCopy function mappings and Metro Mirror or Global
Mirror relationships that use the offline volumes.
2. Run the recovervdisk or recovervdiskbysystem command. (This will only bring
the volume back online so that you can attempt to deal with the data loss.)
Contact IBM Remote Technical Support to help you with recovering from file
volumes that have been corrupted by data lost from the write-cache. They
might ask you to refer to “Recovering a GPFS file system” on page 196 and
help you with interpreting the results from the chkfs CLI command.
386 Storwize V7000 Unified: Problem Determination Guide 2073-720
To Next Page
Loading...
Need help?
General
