STGPOOL Mixup

[foobar2devnull]

Hi all,
It's been a while since I posted here. Looks like I still need the help of my peers!

I think our file storage pool has been configured and then modified and we currently have no more storage left for reclamation.

The way I understand it is that a file storage pool can be configured in one of two ways.

1) Scratch=0 and create all the volumes by hand
2) Scratch=X and TSM will create the volumes as needed with a max of X

What I believe happened is that one person set it up as option 1 and another came by and changed the scratch from 0 to 2000.

I cannot distinguish between the volumes as no prefix seems to have been made on the file (0000000, 0000001, ...)

Now I could be wrong about this but right now,
- Volumes are healthy (read/write)
- I am unable to reclaim (ANR1893E)
- I am unable to move data (ANR1893E)

                    Storage Pool Name: PF01
                    Storage Pool Type: Primary
                    Device Class Name: FILE
                         Storage Type: DEVCLASS
                           Cloud Type:
                            Cloud URL:
                       Cloud Identity:
                       Cloud Location:
                   Estimated Capacity: 99,909 G
                   Space Trigger Util: 80.0
                             Pct Util: 80.0
                             Pct Migr: 80.0
                          Pct Logical: 83.1
                         High Mig Pct: 90
                          Low Mig Pct: 70
                      Migration Delay: 0
                   Migration Continue: Yes
                  Migration Processes: 1
                Reclamation Processes: 2
                    Next Storage Pool:
                 Reclaim Storage Pool:
               Maximum Size Threshold: No Limit
                               Access: Read/Write
                          Description:
                    Overflow Location:
                Cache Migrated Files?:
                           Collocate?: No
                Reclamation Threshold: 60
            Offsite Reclamation Limit:
      Maximum Scratch Volumes Allowed: 2,000
       Number of Scratch Volumes Used: 149
        Delay Period for Volume Reuse: 4 Day(s)
               Migration in Progress?: No
                 Amount Migrated (MB): 0.00
     Elapsed Migration Time (seconds): 0
             Reclamation in Progress?: No
       Last Update by (administrator): JDOE
                Last Update Date/Time: 05/14/2018 13:52:28
             Storage Pool Data Format: Native
                 Copy Storage Pool(s):
                  Active Data Pool(s):
              Continue Copy on Error?: Yes
                             CRC Data: No
                     Reclamation Type: Threshold
          Overwrite Data when Deleted:
                    Deduplicate Data?: Yes
 Processes For Identifying Duplicates: 3
                           Compressed:
                Deduplication Savings: 48,354 G (43.56%)
                  Compression Savings:
                    Total Space Saved: 48,354 G (43.56%)
                       Auto-copy Mode: Client
Contains Data Deduplicated by Client?: Yes
         Maximum Simultaneous Writers:
              Protection Storage Pool:
              Date of Last Protection:
         Deduplicate Requires Backup?:
                            Encrypted:
                   Space Utilized(MB):

I have a system volume group I could add to the storage to start reclamation but I only want to do this once I have identified the problem.

Any advice is welcome.
Thank you all.

 

[foobar2devnull]

I was to quick to ask for help.

I ran the following query that helped show my initial analysis was correct and that there is in fact a naming difference.

>select cast(volume_name as char(50)), cast(chg_time as char(12)), cast(chg_admin as char(10)) from volumes where stgpool_name = 'PF01'

/home/tsminst1/file/file1/000005D                       2015-08-13-0      JDOE     
/home/tsminst1/file/file1/000005E                       2015-08-13-0      JDOE     
/home/tsminst1/file/file1/00007ECB.BFS                  2018-05-15-0                 
/home/tsminst1/file/file1/00007ED2.BFS                  2018-05-15-0                 
/home/tsminst1/file/file10/0000000                      2015-08-11-0      JDOE

All I need to do now (feel free to correct me if you think I am wrong), is
- set maxscratch to 0
- add a VG to the dev to have a bit of space to start reclamation
- set the 2018 (BFS) files read only
- move the data off the volumes (2018)
- remove the volumes (2018)
- reclaim
- remove VG from dev

This is for anyone who might make the same mistake I did.