📖 ~1 min read
Table of contents
Symptom & Impact
sysdumpdev -L reports the last dump was incomplete or failed.
Environment & Reproduction
AIX 7.2 LPAR with dump LV smaller than required by current memory.
Root Cause Analysis
Memory grew via DLPAR but the dump LV was never resized.
Quick Triage
Run sysdumpdev -e to estimate required dump size in bytes.
Step-by-Step Diagnosis
Compare estimate with lslv -l lg_dumplv to see current size.

Solution – Primary Fix
Extend the dump LV: extendlv lg_dumplv N where N covers the estimate.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Create a new dump LV and point sysdumpdev -P -p /dev/newdump at it.
Verification & Acceptance Criteria
sysdumpdev -e fits inside lg_dumplv and a forced dump completes cleanly.
Rollback Plan
Re-point sysdumpdev back to the previous LV if extension causes issues.
Prevention & Hardening
Re-check after every DLPAR memory change and after upgrades.
Related Errors & Cross-Refs
Pairs with DUMP_INCOMPLETE errpt entries after a crash.
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 Docs: sysdumpdev, lg_dumplv sizing guidance.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.