IBM AIX 7.1 – Common Problem 230 – 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 and JFS2 writes return I/O errors on the VG.

Environment & Reproduction

Triggered after path loss, disk replacement, or interrupted varyonvg/migratepv.

Root Cause Analysis

Mirror copies are out of sync because one PV became unavailable during writes.

Quick Triage

Run lsvg -l vgname and lsvg -p vgname to spot stale partitions and missing PVs.

Step-by-Step Diagnosis

Use lspv -l hdiskN and errpt to identify which PV holds stale partitions.

Solution – Primary Fix

Resync mirrors with syncvg -p hdiskN or syncvg -v vgname after restoring the PV.

Solution – Alternative Approaches

If a PV is permanently failed, reducevg vgname hdiskN and re-mirror with mklvcopy.

Verification & Acceptance Criteria

lsvg -l reports zero stale PPs and syncvg returns 0.

Rollback Plan

Stop syncvg with kill and let varyoffvg/varyonvg restore the previous state.

Prevention & Hardening

Run syncvg from cron and alert on stale PPs via custom errnotify entries.

Related Errors & Cross-Refs

Related to disk hardware errors and JFS2 mount failures on the same VG.

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

View all aix-7.1 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

IBM AIX 7.2 LVM administration and syncvg references.