ANR0984I Active disk pool reclamation... There is insufficient space in storage pool

[foobar2devnull]

Hi all,

I am getting the following error which is quite straight forward:

tsm>RECLAIM STGPOOL PA01BRU WAIT=YES THRESHOLD=50 DURATION=420

ANR0984I Process 654 for SPACE RECLAMATION started in the FOREGROUND at 12:33:12 PM.
ANR2110I RECLAIM STGPOOL started as process 654.
ANR4930I Reclamation process 654 started for primary storage pool PA01BRU manually, threshold=50, duration=420.
ANR1040I Space reclamation started for volume /tsmfile/00000984.BFS, storage pool PA01BRU (process number 654).
ANR1044I Removable volume /tsmfile/00000982.BFS is required for space reclamation.
ANR1044I Removable volume /tsmfile/00000984.BFS is required for space reclamation.
ANR1044I Removable volume /tsmfile/00000986.BFS is required for space reclamation.
ANR1086E Space reclamation is ended for volume /tsmfile/00000984.BFS. There is insufficient space in storage pool.
ANR0985I Process 654 for SPACE RECLAMATION running in the FOREGROUND completed with completion state FAILURE at 12:33:29 PM.
ANR4936I Reclamation of storage pool PA01BRU has ended. Files reclaimed: 0, Bytes reclaimed: 0, Files reconstructed: 0, Unreadable files: 0.
ANS8001I Return code 4.
​

tsm>q stgpool pa01bru f=d

Storage Pool Name: PA01BRU
Storage Pool Type: Active-Data
Device Class Name: FILE_BRU01
Estimated Capacity: 2,750 G
Space Trigger Util: 88.8
Pct Util: 88.8
Pct Migr:
Pct Logical: 81.0
Migration Processes: 1
Reclamation Processes: 1
Access: Read/Write
Description: Active data pool - File level backups
Collocate?: No
Reclamation Threshold: 100
Offsite Reclamation Limit: No Limit
Maximum Scratch Volumes Allowed: 280
Number of Scratch Volumes Used: 280
Delay Period for Volume Reuse: 0 Day(s)
Reclamation in Progress?: No
Storage Pool Data Format: Native
CRC Data: Yes
Reclamation Type: Threshold
Overwrite Data when Deleted:
Deduplicate Data?: Yes
Processes For Identifying Duplicates: 1
Duplicate Data Not Stored: 2,941 G (58%)
Contains Data Deduplicated by Client?: No

​

I understand that reclamation can't happen because a new scratch volume can't be created to merge the data from the reclaimable volume, so I'm caught in a catch 22 situation.

My questions are:

1) Why am I using all 280 scratch volumes when (if I understand correctly) I am only using 88.8% of the Pool?

2) How can I resolve this considering I can not add extra storage to the Pool or TSM its self?

3) What can I do to get deduplication up to date? Whe I run SHOW DEDUPPENDING PA01BRU I get back ~607586 GB

Would moving nodes away from PA01BRU free up some space and hopefully, expire an entire volume that can then be removed without having to be reclaimed?

Any help would be welcome.

Thanks!

 

[chad_small]

Use the MOVE DATA command to move the data to an alternate volume thereby freeing up space. It's sometime better to use the MOVE DATA command than reclamation.

MOVE DATA PA01BRU

You can put a bunch of reclaimable volumes in a list with WAIT=YES at the end and TSM will process them one at a time and free up space.

 

[foobar2devnull]

Hi Chad,

Thanks a lot for your help. I'll read up on the command.
In the meanwhile, it looks like our consultant had thought about the issue and had a spare 60GB left on the phisical disk. I simply added acouple more scratch volumes (282) ran a reclamation and ended up with only 165 volumes at the end of the reclamation. I then reset the max scratch to 280 and removed a few nodes from the PA.

Thanks again for your advice.