IT48217: DELETE CONTAINER STORAGE POOL DOES NOT FREE UP SPACE

8.2.2.000-IBM-SPSRV-Linuxx86_64
8.2.2.000-IBM-SPSRV-WindowsX64
8.2.2.000-IBM-SPSRV-AIX
8.2.2.000-IBM-SPSRV-Linuxppc64le
8.2.2.000-IBM-SPSRV-Linuxs390x

APAR status

• Closed as program error.

Error description

• Cleanup for empty containers on IBM Storage Protect server may
  not get automatically triggered for container pools if the file
  system directory listed in q stgpooldir for any pool in the
  environment has been manually deleted.
  Cleanup of containers in stgpool1 may be affected even if
  containers belonging to stgpool2 does not have corresponding
  directory in the filesystem.
  No error is seen in Audit container output or actlog regarding
  these missing directories in the filesystem.
   
  The trace with flags SDDIR SDCNTR SDCNTRD SDLOCK SDDEL SDREPAIR
  
  FFDC will display:
  
  XX:XX:XX.XXX [6335482][sddir.c][3828][SdGetDirectorySpace]:Exit:
  
  rc=3330
  XX:XX:XX.XXX [6335482][sdutil.c][10003][SdMonitorThread]:Error
  3330 getting directory space for <dir_path>
  

Local fix

• Recreate the directories with the original name and permission
  on the filesystem to allow the container cleanup to resume.
  Also make sure the containers are not in UNAVAILABLE state.
  All the containers listed in q stgpooldir f=d, for all the
  storage pools should be present in the filesystem.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Storage Protect server users.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• This problem is currently projected to be fixed in level 8.2.2.
  Note that this is subject to change at the discretion of IBM.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels