IT26657: 8.1.6.SERVER MAY CRASH IN ASOPENVOL DURING 'PROTECT STGPOOL' WITH 'TYPE=LOCAL' WHEN USING MORE THAN ONE PROCESS/DRIVE

8.1.7.000-IBM-SPSRV-Linuxppc64le
8.1.7.000-IBM-SPCMS-WindowsX64
8.1.7.000-IBM-SPCMS-WindowsI32
8.1.7.000-IBM-SPCMS-Linuxx86_64
8.1.7.000-IBM-SPOC-WindowsX64
8.1.7.000-IBM-SPOC-Linuxx86_64
8.1.7.000-IBM-SPOC-Linuxs390x
8.1.7.000-IBM-SPOC-LinuxPPC64le
8.1.7.000-IBM-SPOC-AIX
8.1.7.000-IBM-SPSRV-WindowsX64
8.1.7.000-IBM-SPSRV-Linuxx86_64
8.1.7.000-IBM-SPSRV-Linuxs390x
8.1.7.000-IBM-SPSRV-AIX
IBM Spectrum Protect Server V8.1.6.X interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack 7 (V8.1.7) Downloads

APAR status

• Closed as program error.

Error description

• Spectrum Protect server version 8.1.6 can crash during
  'protect stgpool' with 'type=local'.
  
  This crash can happen when the 'PROTECT STGPOOL' command runs
  multiple processes with different tape drives at almost the same
  time.
  The 'PROTECT STGPOOL' process can cause the server to crash when
  switching among these volumes for open and close activity.
  If there is only one drive being used or the open and close
  among different volumes are not at almost the same time, the
  server will not crash.
  
  This does not affect 'PROTECT STGPOOL' with 'type=replserver'
  
  
  Running dbx on AIX platform will show similar stack entries to:
  
  global_lock_ppc_mp() at 0x9000000005cb534
  pthread_cond_signal@AF28_12(??, ??) at 0x9000000005c392c
  pthread_cond_signal(??) at 0x9000000005c2208
  pkSignalCondition(??) at 0x10000ad3c
  AsOpenVol(??, ??, ??, ??, ??, ??) at 0x1009e5274
  AsAcquireAnyWritableVol(??, ??, ??, ??, ??, ??) at 0x1009c7e38
  IPRA.$GetStgpoolOutputVol(??) at 0x100d07078
  asOpenOutputSdStream(??, ??, ??, ??, ??, ??, ??, ??) at
  0x100d06208
  asOpenOutputCopyCntrStream(??, ??, ??, ??, ??, ??, ??) at
  0x100d07e78
  SdOpenOutputTapeStream(??, ??, ??, ??) at 0x1008fb040
  IPRA.$LocalProtectBeginTapeBatch(??) at 0x1008d279c
  LocalBatchInit(??, ??) at 0x1008d2214
  SdProtectBatchInit(??, ??) at 0x1008b88c0
  IPRA.$ProdConsGetWork(??, ??) at 0x1005f3f5c
  PcConsumerThread(??) at 0x1005f3258
  StartThread(0x0) at 0x10000fc9c
  
  Activity log may report errors similar to:
  
  ANR9999D_3315893365 asCloseOutputSdStream(assd.c:1193)
  Thread<49510>: Invalid sequential stream handle: 0.
  
  ANR9999D_4238802752 pvrReleaseMountPoint(pvrmp.c:2024)
  Thread<49510>: Releasing mount point X (devClass = Y, ext=0)
  with invalid state 3.
  
  ANR9999D_4249955442 ShareOpenVolume(mmsshr.c:2792)
  Thread<49509>: Mount volume name (vol_name) does not match
  expected volume name ( for txn commit or abortSERVER).
  
  before the crash occurs.
  
  
  Initial Impact: Medium
  
  IBM Spectrum Protect versions affected:
  Server 8.1.6.x and higher on all supported platforms
  
  | MDVREGR 8.1.6.0-TIV_5698MSV |
  
  Keywords:
  TSM TS001528032 174993 crash abend core protect stg stgpool
  local
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users of the protect stgpool *
  * command with type=local                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available.                           *
  * This problem is currently projected to be fixed in levels    *
  * 8.1.6.100 and 8.1.7.                                         *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, Linux, and Windows.
  Platforms fixed: AIX, Linux, and Windows.
  

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

• R81A PSY

     UP

• R81L PSY

     UP

• R81W PSY

     UP