kdump fails on RHEL5 with "No space left on device" error messages on console
Issue
- When a crash dump is triggered, either because of a system fault, or manually with SysRq, the kdump process begins, but doesn't complete and produce a core
- While the kdump kernel is booting, one or more
No space left on devicemessages are seen, e.g.:
mknod: /dev/sdwf: No space left on device
mkdir: Cannot create directory `/dev/vg_root': No space left on device
- You may need to watch carefully, or replay a console log to see these errors, since they may be pushed off the screen by other later errors.
Environment
- Red Hat Enterprise Linux 5 (RHEL5)
- (Usually) a large number of available LUNs or other devices
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.