IT05874: INCORRECT BEHAVIOR WHEN ATTEMPTING TO WRITE TO STORAGE POOL VOLUMES ON READ-ONLY FILESYSTEMS

7.1.3.000-TIV-TSMSRV-WIN
7.1.3.000-TIV-TSMSRV-SolarisSPARC
7.1.3.000-TIV-TSMSRV-Linuxx86_64
7.1.3.000-TIV-TSMSRV-Linuxs390x
7.1.3.000-TIV-TSMSRV-Linuxppc64
7.1.3.000-TIV-TSMSRV-HP-UX
7.1.3.000-TIV-TSMSRV-AIX

APAR status

• Closed as program error.

Error description

• If a filesystem associated with a FILE device class is mounted
  as read-only, or becomes read-only as the result of some error
  condition, the Tivoli Storage Manager server does not properly
  handle failed attempts to write to new and/or existing volumes
  on the affected filesystem.  When attempting to append data to
  an existing storage pool volume, errors similar to the following
  may be seen in the activity log:
  
     ANR9905W Unable to open file /FILEPOOL/00000001.BFS.
     Read-only file system.
     ANR8501E System return code 22 received opening volume
     /FILEPOOL/00000001.BFS with file name /filepool/00000001.bfs.
     ANR1401W Mount request denied for volume
     /FILEPOOL/00000001.BFS - mount failed.
  
  The Tivoli Storage Manager server will attempt repeatedly to
  access the same volume resulting in unnecessary session and/or
  process failures.  The expectation is that, after the initial
  write failure, the server would update the access for the volume
  to read-only to prevent further attempts to write data to the
  volume.
  
  When attempting to write data to a new volume on a read-only
  filesystem, the Tivoli Storage Manager server will successfully
  create the scratch volume, but attempts to write data to the
  volume will fail with errors similar to the following:
  
     ANR1340I Scratch volume /FILEPOOL/00000001.BFS is now defined
     in storage pool FILEPOOL.
     ANR8503E A failure occurred in writing to volume
     /FILEPOOL/00000001.BFS.
     ANR1411W Access mode for volume /FILEPOOL/00000001.BFS now
     set to "read-only" due to write error.
  
  The access for the empty volume is then updated to read-only and
  the server proceeds to create a new scratch volume in the same
  filesystem.  This behavior may repeat until the defined storage
  pool limit for scratch volumes has been reached.  The Tivoli
  Storage Manager server should, after the initial write failure,
  only attempt to create new scratch volumes on another directory
  path, if possible.
  
  Tivoli Storage Manager Versions Affected:
  All versions and platforms
  
  Initial Impact:
  Low
  
  Additional Keywords:
  ANR9905W ANR8501E ANR8503E EROFS errno 30
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 7.1.3. Note that this is      *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Solaris, 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

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71W PSY

     UP

• R71S PSY

     UP