Symptom

When using coredump to troubleshoot crashes on ASA, it can happen that there is no coredump saved after a crash. In the output of show coredump log, you will find something similar to this: Coredump Aborted as the complete coredump could not be written to flash Filesystem full on 'disk0', current coredump size bytes too big for allocated filesystem

Conditions

The coredump feature has been enabled and a coredump filesystem (pre-allocated disk space) created. This is usually seen when troubleshooting crashes that happen after a few weeks, on ASAs that are busy and allocate a lot of RAM.

Workaround

Allocating more space to the coredump may help, but the only way to be sure is to have a CF card large enough to contain the full memory, and allocate corresponding space to the coredump filesystem.

Further Problem Description