Directory stgpool container stays "unavailable" after audit.

[daviddeleeuw1]

Hi,

I have a number of containers in "unavailable" status. I am not able to get them accessible again, even after audit.
I tried:

Audit action=Removed, action=ScanDamaged, action=scanall


Protect: TSMMED>q container \\xxx\tsmc10\0c\0000000000000
c26.dcf

Container: \\xxx\tsmc10\0c\0000000000000c26.dcf
Storage Pool Name: CPOOL
Container Type: Dedup
State: Unavailable


Protect: TSMMED>audit container \\xxx\tsmc10\0c\000000000
0000c26.dcf action=scandamaged
ANS8003I Process number 370 started.
(SESSION: 21314)
15-05-2020 18:38:00 ANR2017I Administrator TSMUSER issued command: AUDIT
CONTAINER \\xxx\tsmc10\0c\0000000-
000000c26.dcf action=scandamaged (SESSION: 21102)
15-05-2020 18:38:00 ANR0984I Process 370 for AUDIT CONTAINER started in the
BACKGROUND at 18:38:00. (SESSION: 21102, PROCESS: 370)
15-05-2020 18:38:00 ANR4446I No damaged data was identified by the AUDIT
CONTAINER command (process ID 370). (SESSION: 21102,
PROCESS: 370)
15-05-2020 18:38:00 ANR4013I Audit container process 370 completed audit of 0
containers; 0 successfully audited containers, 0 failed
audited containers. (SESSION: 21102, PROCESS: 370)
15-05-2020 18:38:00 ANR0985I Process 370 for AUDIT CONTAINER running in the
BACKGROUND completed with completion state SUCCESS at
18:38:00. (SESSION: 21102, PROCESS: 370)

Protect: TSMMED>q container \\xxx\tsmc10\0c\0000000000000
c26.dcf

Container: \\xxx\tsmc10\0c\0000000000000c26.dcf
Storage Pool Name: CPOOL
Container Type: Dedup
State: Unavailable

The server is on 8.1.9
Now I am writing this I noticed "0 successfully audited containers, 0 failed audited containers"
Did tsm not "find" the container ? When checking the container file, it is where it is supposed to be, and did not change since April 27.
Any ideas ?
Thanks
David de Leeuw
Ben-Gurion University of the Negev
Beer Sheva
Israel

 

[daviddeleeuw1]

I ran "q container state=unavailable", copied the output, changed it in an editor to a script, and ran the script line by line with "audit container xxx action=scanall wait=yes", and now it fixes the issue. Probably some typo issue with my first attempt. Proposal for the next TSM Version: add the "state=" on the audit command, such as:
audit container state=unavail action=scanall
to try and repair all unavailable containers.
Thanks
David

 

[marclant]

The containers have to be available in order to be audited. You will need to do update stgpooldir {pool_name] {directory_name} access=readwrite.

Audit container is meant to validate the content of a container, not to change the state.