Troubleshooting
Problem
When the command "move container <container name>" successfully completes, the status of the container becomes 'Pending' . 'Pending' means that the container is pending deletion. After the days of the reusedelay parameter on the storage pool expires, the container should be deleted.
Even if the days of the reusedelay on the storage pool has expired, however, the directory container in pending status may not be deleted.
Symptom
A move container command successfully completed, as below:
(Excerpt from the server activity log)
--------->>
ANR2017I Administrator ADMINISTRATOR issued command: MOVE CONTAINER <container name>
(Excerpt from the server activity log)
--------->>
ANR2017I Administrator ADMINISTRATOR issued command: MOVE CONTAINER <container name>
.....
ANR0204I The container state for <container name> is updated from AVAILABLE to PENDING.
ANR0986I Process nnn for move container running in the BACKGROUND processed nnnnn items for a total of nnnnnn bytes with a completion state of SUCCESS at hh:mm:ss .
<<----------
ANR0204I The container state for <container name> is updated from AVAILABLE to PENDING.
ANR0986I Process nnn for move container running in the BACKGROUND processed nnnnn items for a total of nnnnnn bytes with a completion state of SUCCESS at hh:mm:ss .
<<----------
Then, query container command showed that the target container became in pending status, as below:
--------->>
tsm: SERVER1>query container <container name>
--------->>
tsm: SERVER1>query container <container name>
Container Storage Pool Name Container type State
----------------------- -------------------- ------------------ -----------
<container name> <stgpool name> Dedup Pending
<<----------
----------------------- -------------------- ------------------ -----------
<container name> <stgpool name> Dedup Pending
<<----------
However, even after the days of the value of reusedelay parameter passed, the container was still leaving in pending status.
Cause
Generally, the move container should move all data from old container to new container. However, some chunks may be skipped and still left in old container due to some issue during the move container, and then the move container successfully finishes on the server activity log.
After that, although the container has changed to pending status, the container deletion thread does not handle this container deletion.
As result, the pending directory container will remain.
Diagnosing The Problem
You may be able to check this issue as below:
1. Run 'query container <container name> format=detailed command'.
2. Check the output of step 1. When this issue occurs, you may see below:
- The value of State field is pending.
- The value of Free Space is smaller than the value of Maximum Size.
Resolving The Problem
Run the command 'move container <container name>' again to move leftover chunks.
Document Location
Worldwide
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEQVQ","label":"IBM Spectrum Protect"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.6 or later","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Was this topic helpful?
Document Information
Modified date:
10 March 2019
UID
ibm10869230