IBM Support

IT02723: 'DEFINE VOLUME' USING FORMATSIZE REPORTS BEING SUCCESSFUL EVEN IF THE VOLUME IS NOT CREATED WITH DESIRED SIZE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • When using  Tivoli Storage Manager 'define volume' command with
    the 'formatsize' option,
    a volume can be created that is less than the desired size due
    to an environmental limitation.
    
    For example on a Unix system:
    
    ANR2017I Administrator ADMIN issued command: DEFINE
     VOLUME STGPOOL1 /filesystem/vol1.dsm formatsize=200000
     (SESSION: 22)
    ANR0984I Process 53 for DEFINE VOLUME started in the
     BACKGROUND at 17:23:15. (SESSION: 22, PROCESS: 53)
    ANR2491I Volume Creation Process starting for
     /filesystem/vol1.dsm, Process Id 53. (SESSION:
     22, PROCESS: 53)
    ANR2206I Volume /filesystem/vol1.dsm defined in
     storage pool STGPOOL1 (device class DISK). (SESSION: 22,
     PROCESS: 53)
    ANR0986I Process 53 for DEFINE VOLUME running in the
     BACKGROUND processed 1 items for a total of
     209,715,200,000 bytes with a completion state of SUCCESS
     at 17:23:15. (SESSION: 22, PROCESS: 53)
    ANR1305I Disk volume /filesystem/vol1.dsm varied
     online. (SESSION: 22, PROCESS: 53)
    
    So server reports that command successfully created volume with
    size of
    209,715,200,000 bytes, but reviewing the size of
    /filesystem/vol1.dsm in the filesystem
    it shows as only 1GB.
    
    -rw-r--r--    1 tsminst1 tsmsrvrs 1073741312 Mar 27 23:13
    vol1.dsm
    
    'q volume /filesystem/vol1.dsm' shows the volume also as 1GB in
    size.
    
    In this case the cause was tsminst1 having the file ulimit set
    to:
    file(blocks)         2097151
    
    It should be unlimited.
    
    
    
    
    Tivoli Storage Manager versions affected:
    Server 6.2, 6.3 and 7.1 on all platforms
    
    Initial Impact: Medium
    
    Additional Keywords:
    zz62 zz63 zz71 tsm define volume size
    

Local fix

  • Correct environmental limitation and delete volume (if
    empty) and define it  again with correct size.
    If data exists in volume, issue move data to empty it, then
    delete and redefine it.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem is projected to be fixed in a future version of the
     Tivoli Storage Manager server.  Note that this is subject to ch
    ange at the discretion of IBM.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT02723

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63A

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-25

  • Closed date

    2014-07-24

  • Last modified date

    2014-07-24

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

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

Fix information

Applicable component levels

  • R63A PSY

       UP

  • R63L PSY

       UP

  • R71A PSY

       UP

  • R71L PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 63A

Reference #: IT02723

Modified date: 24 July 2014