Where Are Linux Core Dumps Stored?
Where systemd stores crash core dumps on Linux, and how to list and clean them with coredumpctl.
Last updated
Systemd routes crash dumps into a central store under var: compressed core files with journal metadata beside them. The coredumpctl tool lists, extracts and prunes the collection without hand browsing.
Limits in coredump.conf cap total size and age, so old dumps rotate on their own. Disabled collection shows as empty output rather than errors. Copy entries with journal context attached for reports developers can use.
Where Linux stores this, by platform
/var/lib/systemd/coredump
Compressed cores with journal metadata under var. Manage with coredumpctl, not file copies. Limits in coredump.conf rotate old entries automatically.
Frequently asked questions
How do I clean old core dumps?
Run coredumpctl list to see entries, then coredumpctl clean to prune by age or size. Storage limits live in coredump.conf. Dumps compress by default, but repeated crashes still fill small roots.
How do I debug one crash from a dump?
Run coredumpctl dump with the entry id to extract a core file, then debug it with gdb. The journal entry beside it holds the crash context. Copy both together for bug reports.
Notice an outdated path? Let us know.