PI56221: HASH COLLISION FINDS INCORRECT VOB IN INTERNAL MOUNT TABLE LEADING TO EACCESS AND ESTALE ERRORS

Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 11 (8.0.1.11) for 8.0.1
Rational ClearCase Fix Pack 1 (9.0.0.1) for 9.0
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 12 (8.0.1.12) for 8.0.1
Rational ClearCase Fix Pack 2 (9.0.0.2) for 9.0
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 13 (8.0.1.13) for 8.0.1
Rational ClearCase Fix Pack 3 (9.0.0.3) for 9.0
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0
Rational ClearCase Fix Pack 14 (8.0.1.14) for 8.0.1
Rational ClearCase Fix Pack 4 (9.0.0.4) for 9.0
Rational ClearCase Fix Pack 15 (8.0.1.15) for 8.0.1
Rational ClearCase Fix Pack 5 (9.0.0.5) for 9.0
Rational ClearCase Fix Pack 6 (9.0.0.6) for 9.0
Rational ClearCase Fix Pack 16 (8.0.1.16) for 8.0.1
Rational ClearCase Fix Pack 17 (8.0.1.17) for 8.0.1
Rational ClearCase Fix Pack 18 (8.0.1.18) for 8.0.1
Rational ClearCase Fix Pack 19 (8.0.1.19) for 8.0.1
Rational ClearCase Fix Pack 20 (8.0.1.20) for 8.0.1
Rational ClearCase Fix Pack 21 (8.0.1.21) for 8.0.1
Rational ClearCase Fix Pack 22 (8.0.1.22) for 8.0.1
Rational ClearCase Fix Pack 23 (8.0.1.23) for 8.0.1
Rational ClearCase Fix Pack 24 (8.0.1.24) for 8.0.1
Rational ClearCase Fix Pack 25 (8.0.1.25) for 8.0.1

APAR status

• Closed as program error.

Error description

• In the IBM Rational ClearCase VOB filehandle there is a hash of
  the superblock pointer, which is used internally within the
  ClearCase mount table. When these two superblocks are hashed to
  the same value ClearCase will always choose the oldest mount
  first. This leads to EACCESS and ESTALE errors trying to access
  file elements witin the VOB mounted at a later time.
  
  WORKAROUND:
  None.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of IBM Rational ClearCase on systems which export      *
  * view-VOB combinations for non-ClearCase access.              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In some cases IBM Rational ClearCase users would find that   *
  * they could not access views and VOBs exported using          *
  * non-ClearCase access and would receive STALE NFS FILE HANDLE *
  * errors.                                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A correction was made in ClearCase versions 8.0.0.18, 8.0.1.11,
  and 9.0.0.1 to eliminate the stale file handle errors for
  exported VOBs.
  

Temporary fix

Comments

APAR Information

• 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

  CC&CC MSITE WIN

• Fixed component ID

  5724G3300

Applicable component levels

• R800 PSY

     UP

• R801 PSY

     UP

• R900 PSY

     UP