IBM Support

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

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-03 Technology Level with
    * bos.mp64 between and including the 7.1.3.0 and 7.1.3.2
    * levels.
    *************************************************************
    * PROBLEM DESCRIPTION:
    * Customers using jfs2 may see errpt showing the filesystem
    * requires fsck with an error code of 0x34 (ESTALE).
    * LABEL:          J2_FSCK_REQUIRED
    * ERROR CODE
    * 0000 0034
    * However when fsck is run, it reports that no corruption was
    * encountered.
    *
    * In this case, you may be experiencing a bug in jfs2 code
    * that can cause it to mistakenly mark the filesystem as
    * needing repair when it is not really needed.  If the
    * situation is encountered, you should:
    *  1. install this fix to ensure jfs2 will not mark the
    *     filesystem dirty by mistake
    *  2. unmount, run fsck, and remount to mark the filesystem
    *     clean
    *************************************************************
    * RECOMMENDATION:
    * Install APAR IV57361.
    * Prior to fix availability, an interim fix is available from
    * either
    * ftp://aix.software.ibm.com/aix/ifixes/iv57361/
    * https://aix.software.ibm.com/aix/ifixes/iv57361/
    *************************************************************
    

Problem conclusion

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

Temporary fix

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

Comments

  • 6100-07 - use AIX APAR IV59227
    6100-08 - use AIX APAR IV59225
    6100-09 - use AIX APAR IV59100
    6100-09 - use AIX APAR IV59100
    6100-09 - use AIX APAR IV59100
    7100-01 - use AIX APAR IV59232
    7100-02 - use AIX APAR IV59229
    7100-03 - use AIX APAR IV57361
    7100-03 - use AIX APAR IV57361
    7100-03 - use AIX APAR IV57361
    7100-04 - use AIX APAR IV59708
    

APAR Information

  • APAR number

    IV57361

  • Reported component name

    AIX V7.1

  • Reported component ID

    5765H4000

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Submitted date

    2014-03-24

  • Closed date

    2014-04-10

  • Last modified date

    2016-05-10

Fix information

  • Fixed component name

    AIX V7.1

  • Fixed component ID

    5765H4000

Applicable component levels

  • R710 PSY U858978

       UP14/05/22 I 1000 «

PTF to Fileset Mapping



Document information

More support for: AIX Enterprise Edition

Software version: 710

Operating system(s): AIX

Reference #: IV57361

Modified date: 10 May 2016