IBM Support

IT11095: FILE POOL SCRATCH VOL ALLOCATION CHOOSES DIR WITH LITTLE SPACE LEFT ON FILESYSTEM/VOLUME OVER DIR WITH MORE AVAILABLE SPACE.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When multiple directories are defined in a file device class,
    scratch volume allocation does not consider the current
    available space on the filesystem/volume of the directory
    selected. This can result in the creation of very small volumes
    or in some extreme cases empty volumes. This is true even when
    other directories in the device class reside on
    filesystems/volumes with signigicant free space. File pool
    scratch volume allocation should take into consideration the
    space remaining on the filesystem/volume for all directories to
    create a new volume with the full maxcap volume size whenever
    possible.
    In RedHat environments the problem can be compounded by the fact
    that there is 16MB of system reserved space that cannot be
    written to but is reported as not yet used. In this environment
    the creation of empty volumes has been reported as a regular
    occurrence when other directories are available whose
    filesystems have enough free space for a full maxcap sized new
    scratch volume. This issue should be addressed by the change
    from the current directory selection to one taking the amount of
    space actually available into consideration.
    Tivoli Storage Manager Versions Affected:
    V6 and V7 servers all platforms
    Initial Impact: Medium
    Additional Keywords:
    TSM Spectrum Protect
    

Local fix

  • Use only predefined file pool volumes or ensure all
    filespaces/volumes with file device class directories residing
    always have enough free space on them for at least one new
    scratch volume given the estimated capacity of device class.
    

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.5. 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 number

    IT11095

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-09-08

  • Closed date

    2015-10-15

  • Last modified date

    2015-10-15

  • 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

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 7.1.3

Reference #: IT11095

Modified date: 15 October 2015