IBM Support

IT00643: DATA MOVEMENTS OR DATA COPIES OF A DEDUPLICATED STGPOOL VOLUME MIGHT RESULT IN INVALIDATED DEDUPLICATION LINKS - ANR4895E

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A data movement, or data copy, process might end in failure when
    processing a volume located in a deduplicated storage pool.
    The following error would be reported within the failing
    process:
    
    ANR4895E Deduplicated bitfile 123456789 on volume /volume01.dsm
    has invalid links.
    
    The cause of the ANR4895E message and invalid termination of the
    process, are the existence of duplicate aggregates being stored
    in the same storage pool. These files contained within those
    aggregates have conflicting references in the deduplication
    catalog of the Tivoli Storage Manager server.
    
    This is not a deduplication referential integrity problem but
    rather an error in the server for which the server is not
    properly choosing the right deduplication information for each
    aggregate.
    
    
    Customer/L2 Diagnostics:
    These invalidated links will not be reported via a the
    VALIDATE EXTENTS utility.
    
    To check if this APAR does match, the following can be done
    for the reported bitfile from the ANR4895E error:
    
    ANR4895E Deduplicated bitfile 123456789 on volume /volume01.dsm
    has invalid links.
    
    Here is the affected bitfile 123456789.
    From a server command line:
    
    show bfo 123456789
    
    Bitfile Object: 123456789
    **Super-bitfile 123456789 contains following aggregated
    bitfiles,
    Bitfile Id, offset, length, active state or owner, link bfid
      AAAAAAAAAA     0             49004         ZZZZZZZZZZ
      BBBBBBBBBB     0             0             YYYYYYYYYY
    
    **Archival Bitfile Entry
       Bitfile Type: PRIMARY  Storage Format: 22
       Bitfile Size: 49068  Number of Segments: 1, flags: 3
       Storage Pool ID: 5  Volume ID: 987  Volume Name:
    /volume01.dsm
    
    -> This returns here two aggregated bitfiles AAAAAAAAAA and
       BBBBBBBBBB
    
    SHOW BFO against this aggregated bitfiles returned the
    following:
    
    show bfo AAAAAAAAAA
    Bitfile Object: AAAAAAAAAA
    
    **Sub-bitfile AAAAAAAAA is stored in the following aggregate(s)
       Super-bitfile: CCCCCCCCCC, Offset: 0, Length 0, Deduped: F
       Super-bitfile: 123456789, Offset: 0, Length 49004, Deduped: F
    
    -> The bitfile AAAAAAAAAA has two Super-bitfiles
       CCCCCCCCCC is an "empty" chunk
       123456789 is a base chunk
    
    
    show bfo BBBBBBBBBB
    
    Bitfile Object: BBBBBBBBBB
    
    **Sub-bitfile BBBBBBBBBB is stored in the following aggregate(s)
       Super-bitfile: CCCCCCCCCC, Offset: 0, Length 71895, Deduped:
    F
       Super-bitfile: 123456789, Offset: 0, Length 0, Deduped: F
    
    -> The bitfile AAAAAAAAAA has two Super-bitfiles
       CCCCCCCCCC is a base chunk
       123456789 is an "empty" chunk
    
    In this case there are two "deleted" aliases in the same pool.
    Each alias contains a base chunk and an "empty" chunk.
    
    Tivoli Storage Manager Versions Affected:
    Tivoli Storage Manager Server 6.1, 6.2, 6.3 and 7.1 on all
    supported platforms
    
    Initial Impact:
    low
    
    Additional Keywords:
    TSM zz61 zz62 zz63 zz71 invalid link
    

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 levels 6.3.5 and 7.1.1. 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

    IT00643

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-31

  • Closed date

    2014-05-03

  • Last modified date

    2014-05-03

  • 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

  • R63A PSY

       UP

  • R63L PSY

       UP

  • R63H PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"63L","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
03 May 2014