IBM Support

IJ37747: HEALTH MONITORING IS RAISING AN ILL_UNBALANCED_FS DEGRADED HEALTH EVENT WHEN ADDING NEW DISKS TO A FILES YSTEM

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When adding a new disk to a file system, health monitoring will
    raise an ill_unbalanced_fs degraded health event as the file
    system will be unbalanced.  This degraded health event does not
    reflect the current recommendation
    of when to use the mmrestripefs
    command, and so the degraded health event's severity is to sever
    and is being changed from a degraded severity level to being a
    TIP severity level.
    

Local fix

  • The ill_unbalanced_fs event can be added to the "ignore events"
    list in the mmsysmonitor.conf file. After mmsysmon is restarted,
    this event will be ignored by mmhealth and will not cause any
    unbalanced file systems to show as being degraded.
    

Problem summary

  • When adding a new disk to a file system, health monitoring will
    raise an ill_unbalanced_fs degraded health event as the file
    system will be unbalanced.  This degraded health event does not
    reflect the current recommendation
    of when to use the mmrestripefs
    command, and so the degraded health event's severity is to sever
    and is being changed from a degraded severity level to being a
    TIP severity level.
    

Problem conclusion

  • This problem is fixed in 5.1.2  PTF  3
    To see all Spectrum Scale APARs and
    their respective fix solutions refer to page
    https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
    apars.html
    
    Benefits of the solution:
    By changing the health event to a TIP,  the file system will
    no longer appear to be degraded.  A TIP (suggestion)
    event will be shown instead, and this TIP event is able to
    be hidden so that it will no longer show up in the mmhealth
    display.
    
    Work around:
    The ill_unbalanced_fs event can be added to the "ignore events"
    list in the mmsysmonitor.conf file. After mmsysmon is restarted,
    this event will be ignored by mmhealth and will not cause any
    unbalanced file systems to show as being degraded.
    
    Problem trigger:
    Adding a new disk to an existing file system.
    
    Symptom:  Error output/message
    
    Platforms affected: ALL
    
    Functional Area affected: System Health
    
    Customer Impact:  Suggested
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ37747

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    512

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-02-10

  • Closed date

    2022-02-10

  • Last modified date

    2022-02-10

  • 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

    SPEC SCALE STD

  • Fixed component ID

    5737F33AP

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"512","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
10 February 2022