PK36055: TSM SERVER HANG DUE TO SERIALIZATION PROBLEM WITHIN RECLAMATION PROCESS

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The TSM Server may get into a temporary hang state after
    a reclamation process is started. If reclamation encounters
    a volume that is empty but cannot be deleted then a repair
    function is invoked. It is this repair function that can cause
    a hang condition within the TSM Server.
    .
    NOTE: The hang should resolve itself after the amount of
    time specified by the resourcetimeout has expired based
    on when the reclamation repair kicked off. The default
    resourcetimeout value is 60 minutes. However, depending
    upon the number and type of threads involved in the
    hang, the hang symptoms may continue beyond the
    resourcetimeout.
    .
    Platforms affected: All TSM 5.2 and 5.3 Servers
    .
    .
    If the TSM Server becomes partially hung, meaning
    that an admin session can still be opened and most
    queries complete, the following series of show commands
    should be issued every 10-15 minutes during the hang
    for a period of 40-60 minutes. If this problem is being
    encountered, the following thread state will be found in the
    show thread output:
    <show threads, show txnt and show locks>
    .
    pkWaitCondition
    tmLock
    AfLockBfRoot
    AfExistsSegmentc
    bfExistsSegment
    AsRepairOrphanSegments
    ssRepairVolSegInfo
    DoReclamation
    AfReclamationThread
    StartThread
    .
    NOTE: Different platforms may or may not show the callstack
    of each thread. If the callstack is unavailable within show
    threads, a core dump may have to be generated to verify this
    problem.
    .
    Initial Impact: Medium
    .
    Additional Keywords:  repair volseg ssRepairVolSegInfo
                          AsLockVolRoot AsLockVolId AfLockBfRoot
                          AF_LOCK_BFROOT 48051
    

Local fix

  • 1) Make sure that reclamation processes do not run concurrently
    with other TSM Server processes/sessions
    2) Quiesce the TSM Server completely and run the Repair
    Stgvol utility. The TSM Server must be at 5.2.8+ or 5.3.3+ in
    order to run this utility.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All TSM V5.2 and V5.3 Servers on all         *
    *                 platforms.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: See Error Description                   *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 5.2.10 and 5.3.5. Note that this   *
    *                 is subject to change at the discretion of    *
    *                 IBM.                                         *
    ****************************************************************
    Locking conflicts were causing 2 threads to deadlock, tieing up
    resources and locks.  The most noticeable effect is that
    reclamation would hang, then free itself up after approximately
    60 minutes.
    

Problem conclusion

  • The locking conflict has been corrected, thus eliminating the
    hang condition.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK36055

  • Reported component name

    TSM FOR OS/390

  • Reported component ID

    5698ISMVS

  • Reported release

    530

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-12-11

  • Closed date

    2006-12-11

  • Last modified date

    2008-01-03

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

    IC50737

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

Fix information

  • Fixed component name

    TSM FOR OS/390

  • Fixed component ID

    5698ISMVS

Applicable component levels

  • R530 PSY UK23711

       UP07/04/10 P F704

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

530

Reference #:

PK36055

Modified date:

2008-01-03

Translate my page

Machine Translation

Content navigation