IBM Support

IJ25905: NEWLY-CREATED FILESET STARTS OUT WITH HIGH IN-DOUBT VALUES

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 a new fileset is created, the in-doubt quota shares
    for that fileset should start out at 0.
    
    In some situations, a fileset can be created and start
    out with a non-zero in-doubt value. This can occur
    when a fileset had been deleted previously, and then
    the new fileset re-uses the same ID that the deleted
    fileset had used.
    
    Known impact:
    
    If the in-doubt value is unnecessarily high, then
    the quota limit could be reached long before the
    data or files used actually get that high. It could
    even be possible for the in-doubt value to start
    out so high that no files can be created in the new
    fileset at all.
    
    Normally, the in-doubt will decrease as the actual used
    values are adjusted by the quota manager. In this
    scenario, the bogus in-doubt value cannot be decreased
    because there is no client that can return those quota
    shares.
    
    The in-doubt value for the fileset begins high and
    stays high.
    
    Verification Steps:
    
    The mmrepquota command shows the in-doubt value for
    blocks
    and for file counts. If it is showing a high value for
    either of these for a new fileset, then it could be due
    to this defect.
    
    Recovery action:
    
    Running mmcheckquota will reset all of the in-doubt
    values
    .
    

Local fix

  • Running mmcheckquota will reset all of the in-doubt
    values.
    

Problem summary

  • When a new fileset is created,
     the in-doubt quota shares
     for that fileset should start out at 0.
    
     In some situations, a fileset
     can be created and start
     out with a non-zero in-doubt value.
     This can occur
     when a fileset had been
     deleted previously, and then
     the new fileset re-uses
     the same ID that the deleted
     fileset had used.
    

Problem conclusion

  • Benefits of the solution:
    No more running out of quota before
    you actually run out of quota.
    
    Work Around:
    Running mmcheckquota will reset all
    of the in-doubt values
    
    Problem trigger:
    
    Symptom:
    
    Platforms affected:
    
    ALL Operating System environments
    
    Functional Area affected:
    Quotas
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ25905

  • Reported component name

    SPEC SCALE ADV

  • Reported component ID

    5737F35AP

  • Reported release

    504

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-26

  • Closed date

    2020-08-10

  • Last modified date

    2020-08-10

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

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

    IJ27026

Fix information

  • Fixed component name

    SPEC SCALE ADV

  • Fixed component ID

    5737F35AP

Applicable component levels

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

Document Information

Modified date:
15 August 2020