IBM Support

IJ49580: IO ERR 'NO SUCH DEVICE OR ADDRESS' IF A NSD IS REMOVED LOCALLY

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

  • ABSTRACT:
    IO err "No such device or address" if a NSD is removed
    locally
    
    Error Description:
    
    GPFS will use a NSD locally if it find a local path to
    that NSD disk.
    But GPFS will return "No such device or address" for IO
    operations after a NSD
    disk is unattached/removed from that node, whatever that
    node is a NSD server
    for that NSD disk or not.
    
    Reported in:
    All Storage scale versions.
    
    Known Impact:
    "No such device or address" errors for IO to a NSD if it
    is removed/unattached from that
    node even if that NSD has NSD server defined.
    
    Verification steps:
    Checked if the I/O from GPFS node will return "No such
    device or address"(err 6)
    if the local path to an NSD disappeared from that node.
    
    Recovery action:
    Restart GPFS on that node.
    
    Local Fix:
    No
    

Local fix

Problem summary

  • When the device file for a NSD disk got offline or unattached
    from a node, the I/O issued from that node
    would fail with "No such device or address" error (6), even
    there are other NSD servers defined and
    available for servicing I/O request.
    

Problem conclusion

  • Ensure the I/O operations can be done from a node even its local
     disk device file got offline or unattached from it,
    when there are other NSD servers defined and available for
    service.
    
    This problem is fixed in 5.1.9.2
    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:
    Ensure the I/O operations can be done from a node even its local
    disk device file got offline or unattached from it, when there
    are other NSD servers defined and available for service.
    
    Work around:
    reboot the node.
    
    Problem trigger:
    The disk device got offline or unattached
    from a node.
    
    Symptom:
    I/O error
    
    Platforms affected:
    All Operating Systems
    
    Functional Area affected:
    All Scale Users
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ49580

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    517

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-12-22

  • Closed date

    2024-01-11

  • Last modified date

    2024-01-17

  • 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":"517","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
23 January 2024