IBM AIX 7.3 – Common Problem 104 – 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

lsvg -l shows stale PPs after a path or disk transient failure.

Environment & Reproduction

Mirrored VG where one copy diverged during outage.

Root Cause Analysis

LVM marks PPs stale until syncvg replays writes.

Quick Triage

lsvg -p vgname and lsvg -l vgname to spot stale counts.

Step-by-Step Diagnosis

Identify stale LVs with lslv -m lvname output.

Solution – Primary Fix

Run syncvg -v vgname or syncvg -l lvname to resync.

Solution – Alternative Approaches

Force a fresh mirror with mklvcopy + syncvg if scrub fails.

Verification & Acceptance Criteria

lsvg -l reports 0 stale across all LVs.

Rollback Plan

If sync corrupts data, restore from mksysb or savevg backup.

Prevention & Hardening

Enable bad block relocation and quorum monitoring.

Related Errors & Cross-Refs

Often follows MPIO path flap or HBA reset events.

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

View all aix-7.3 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

IBM Docs: LVM, syncvg, mklvcopy.