IBM AIX 7.2 – Common Problem 249 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

mmmount fails and df does not show the GPFS filesystem; apps see ENOENT on paths.

Environment & Reproduction

Triggered by network partition between nodes, quorum loss, or NSD path failure.

Root Cause Analysis

GPFS cluster manager cannot reach quorum or NSDs are unreachable from the node.

Quick Triage

Run mmgetstate -aLs and mmlsmount all -L to see cluster and mount state.

Step-by-Step Diagnosis

Use mmlsnsd -m and mmhealth node show to identify NSDs in degraded state.

Solution – Primary Fix

Restore SAN paths with cfgmgr/chpath then run mmmount fs all on the node.

Solution – Alternative Approaches

If quorum is lost, start nodes in maintenance order with mmstartup -a.

Verification & Acceptance Criteria

mmlsmount shows the fs mounted on the node and mmhealth reports HEALTHY.

Rollback Plan

mmumount fs and revert to the prior cluster configuration via mmchconfig.

Prevention & Hardening

Use tiebreaker disks for small clusters and monitor mmhealth with snmp.

Related Errors & Cross-Refs

Related to FC path loss, network flaps, and quorum design for GPFS clusters.

Related tutorial: View the step-by-step tutorial for aix-7.2.

View all aix-7.2 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

IBM Spectrum Scale documentation for AIX 7.2 nodes.