Go to main content

Managing Devices in Oracle® Solaris 11.3

Exit Print View

Updated: April 2018
 
 

About Deferred Dump and System Crash Dumps

Oracle Solaris includes a feature called deferred dump. Deferred dump is a mechanism that postpones the writing of a crash dump until a system reboots. When a system panic occurs, a core dump file is generated and preserved in memory. When the system comes back online, the core dump is extracted to the filesystem defined in the dump configuration for dumpadm(1M). Once the dump is written, the system may reboot again to a multi-user configuration. Otherwise, the system proceeds to boot as normal.

Deferred dump takes advantage of Oracle technologies to retain memory across system reboots. The system state during a panic is recorded and preserved in memory for later analysis.


Note -  By default you should always configure a dump device as a backup. After a crash dump, it is possible that there may be insufficient space in the target file system to store the core dump file. See the dumpadm(1M) man page for information on configuring a backup dump device.

Deferred dump specifically benefits Oracle systems that may have no local disks attached, for example, the SPARC M7 series servers. Deferred dump also provides an additional benefit of increasing overall system availability due to the the system returning to a running state more quickly after a kernel panic.

For information about saving a crash dump of the Oracle Solaris operating system, refer to the savecore(1M) man page.