IBM Support

IV59232: JFS2 FS MARKED CORRUPT WHEN USING FIND COMMAND NEEDING FSCK RUN APPLIES TO AIX 7100-01

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A JfS2 FS can be marked corrupt when accessing a lot of
    files(been seen with the
    use of the find command). This results in fsck needing to
    be run the
    next time the FS needs to be mounted. The error report is
    updated with symbol
    addresses indicating problem happened  with the following
    stack :
    
    diRead+000354
    iGet+000DF8
    j2_lookup+000428
    vnop_lookup+0001D4
    lookuppn+000918
    statxat+000320
    
    It is caused by accessing stale metadata.  It occurs
    rarely since
    most of the time the metadata has acceptable data even
    though
    it is stale.  However when it does not have acceptable
    data the FS can be
    marked as corrupt.  The fix of the problem avoids stale
    data from being accessed
    

Local fix

  • No local fix.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:
    * Systems running the 7100-01 Technology Level with the
    * bos.mp64 fileset at or between
    * the 7.1.1.17 and 7.1.1.20 levels.
    ****************************************************************
    * PROBLEM DESCRIPTION:
    * A JfS2 FS can be marked corrupt when accessing a lot of
    * files(been seen with the
    * use of the find command). This results in fsck needing to
    * be run the
    * next time the FS needs to be mounted. The error report is
    * updated with symbol
    * addresses indicating problem happened  with the following
    * stack :
    * diRead+000354
    * iGet+000DF8
    * j2_lookup+000428
    * vnop_lookup+0001D4
    * lookuppn+000918
    * statxat+000320
    * It is caused by accessing stale metadata.  It occurs
    * rarely since
    * most of the time the metadata has acceptable data even
    * though
    * it is stale.  However when it does not have acceptable
    * data the FS can be
    * marked as corrupt.  The fix of the problem avoids stale
    * data from being accessed
    ****************************************************************
    * RECOMMENDATION:
    * Install APAR IV59232.
    ****************************************************************
    

Problem conclusion

  • correct a check on the read into the inode cache.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    IV59232

  • Reported component name

    AIX V7.1

  • Reported component ID

    5765H4000

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Submitted date

    2014-04-14

  • Closed date

    2014-04-14

  • Last modified date

    2016-05-10

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

    IV57361

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

Fix information

  • Fixed component name

    AIX V7.1

  • Fixed component ID

    5765H4000

Applicable component levels

  • R710 PSY U861815

       UP14/08/12 I 1000 «

PTF to Fileset Mapping

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSMV87","label":"AIX 6.1 Enterprise Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMVAX","label":"AIX Express Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG11R","label":"AIX 7.1 HIPERS, APARs and Fixes"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
10 May 2016