IC64848: MIGRATION PROCESS ON A TIVOLI STORAGE MANAGER 6.1 SEVER MAY HANG AFTER RUNNING FOR A PERIOD OF TIME

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The migration process on a Tivoli Storage Manager sever 6.1 may
    seem to hang after the process is running successfully for a
    period of time.
    When this situation is encountered, no bytes nor any files are
    moved anymore: the QUERY PROCESS output does show the same
    statistics for the migrations process(es) all the time.
    Actually this is not really a hang situation as the migration
    process is in a non-terminating loop.
    
    
    Customer/L2 Diagnostics:
    A Tivoli Storage Manager sever trace with traceflags AF BF DF
    shows (here as an example for one bitfile with ID 894522540):
    [...]
    09:33:07.759 [102][dfmigr.c][5467][LockBVSuperNodes]:Pool 1,
    bitfile 0:894522540 skipped to prevent deadlock.
    09:33:07.875 [100][dfutil.c][908][DfLockBitfile]:Acquiring lock
    (sLock) for disk bitfile SrvId=0, BfId=(0.894522540)
    09:33:07.882 [100][dfutil.c][1016][DfUnlockBitfile]:Releasing
    shared lock on disk bitfile SrvId=0, BfId=(0.894522540)
    09:33:08.061 [100][dfmigr.c][5467][LockBVSuperNodes]:Pool 1,
    bitfile 0:894522540 skipped to prevent deadlock.
    09:33:08.182 [102][dfutil.c][908][DfLockBitfile]:Acquiring lock
    (sLock) for disk bitfile SrvId=0, BfId=(0.894522540)
    09:33:08.188 [102][dfutil.c][1016][DfUnlockBitfile]:Releasing
    shared lock on disk bitfile SrvId=0, BfId=(0.894522540)
    [...]
    
    Also thousands of these messages can be seen:
    [...]
    09:33:07.743 [101][dfmigr.c][4889][ReserveCluster]:Process 3
    unable to reserve cluster srvId=0, ck1=92, poolMigContMod=0,
    inUse=0, migContMode=0, damaged=0, underAge=0, pendingShred=0
    for migration from pool DISKPOOL(1).
    09:33:07.744 [100][dfmigr.c][4889][ReserveCluster]:Process 2
    unable to reserve cluster srvId=0, ck1=10, poolMigContMod=0,
    inUse=0, migContMode=0, damaged=0, underAge=0, pendingShred=0
    for migration from pool DISKPOOL(1).
    09:33:07.745 [101][dfmigr.c][4889][ReserveCluster]:Process 3
    unable to reserve cluster srvId=0, ck1=36, poolMigContMod=0,
    inUse=0, migContMode=0, damaged=0, underAge=0, pendingShred=0
    for migration from pool DISKPOOL(1).
    [...]
    
    A SHOW LOCKS command does show a very high number of locks of
    type 93001
    slot -> 255:
    LockDesc: Type=93001(bv Supernode), NameSpace=0, SummMode=xLock,
    Key='10372:15317'
      Holder: (bvutil.c:4486 Thread 117) Tsn=0:5548, Mode=xLock
    LockDesc: Type=93001(bv Supernode), NameSpace=0, SummMode=xLock,
    Key='10372:5317'
      Holder: (bvutil.c:4486 Thread 127) Tsn=0:2543, Mode=xLock
    LockDesc: Type=93001(bv Supernode), NameSpace=0, SummMode=xLock,
    Key='10350:1944'
      Holder: (bvutil.c:4486 Thread 114) Tsn=0:2341, Mode=xLock
    LockDesc: Type=93001(bv Supernode), NameSpace=0, SummMode=xLock,
    Key='10360:1944'
      Holder: (bvutil.c:4486 Thread 115) Tsn=0:2275, Mode=xLock
    LockDesc: Type=93001(bv Supernode), NameSpace=0, SummMode=xLock,
    Key='10348:337'
      Holder: (bvutil.c:4486 Thread 101) Tsn=0:1585, Mode=xLock
    LockDesc: Type=93001(bv Supernode), NameSpace=0, SummMode=xLock,
    Key='10344:1944'
      Holder: (bvutil.c:4486 Thread 103) Tsn=0:231, Mode=xLock
    
    
    Tivoli Storage Manager Versions Affected:
    Tivoli Storage Manager 6.1 servers on all supported platforms.
    
    
    Initial Impact:
    High
    
    
    Additional Keywords:
    zz61 loop looping hang hanging waiting migrate migr TSM
    

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 6.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, Sun Solaris, Linux, and
    Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC64848

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    61S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-01

  • Closed date

    2009-12-04

  • Last modified date

    2009-12-04

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61L PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

61S

Reference #:

IC64848

Modified date:

2009-12-04

Translate my page

Machine Translation

Content navigation