JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Troubleshooting Typical Issues in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


1.  Managing System Crash Information (Tasks)

What's New in Managing System Crash Information

Changes to savecore Behavior

System Crashes (Overview)

System Crash Dump Files

Saving Crash Dumps

Managing System Crash Dump Information With the dumpadm Command

How the dumpadm Command Works

Managing System Crash Dump Information

Managing System Crash Dump Information (Task Map)

How to Display the Current Crash Dump Configuration

How to Modify a Crash Dump Configuration

How to Examine Crash Dump Information

How to Recover From a Full Crash Dump Directory (Optional)

How to Disable or Enable the Saving of Crash Dumps

2.  Managing Core Files (Tasks)

3.  Troubleshooting System and Software Problems (Tasks)

4.  Troubleshooting Miscellaneous System and Software Problems (Tasks)


System Crashes (Overview)

Keep the following key points in mind when you are working with system crash information:

System crashes can occur due to hardware malfunctions, I/O problems, and software errors. If the system crashes, it will display an error message on the console, and then write a copy of its physical memory to the dump device. The system will then reboot automatically. When the system reboots, the savecore command is executed to retrieve the data from the dump device and write the saved crash dump to your savecore directory. The saved crash dump files provide invaluable information to aid in diagnosing the problem.

The crash dump information is written in a compressed format to the vmdump.n file, where n is an integer that identifies the crash dump. Afterwards, the savecore command can be invoked on the same system or another system to expand the compressed crash dump to a pair of files that are named unix.n and vmcore.n. The directory in which the crash dump is saved upon reboot can also be configured by using the dumpadm command.

Dedicated ZFS volumes are used for swap and dump areas. After an installation, you might need to adjust the size of swap and dump devices or possibly recreate the swam and dump volumes. For instructions, see Managing Your ZFS Swap and Dump Devices in Oracle Solaris 11.1 Administration: ZFS File Systems.

System Crash Dump Files

The savecore command runs automatically after a system crash to retrieve the crash dump information from the dump device and writes a pair of files, called unix.x and vmcore.x, where x identifies the dump sequence number. Together, these files represent the saved system crash dump information.

Note - Crash dump files are sometimes confused with core files, which are images of user applications that are written when the application terminates abnormally.

Crash dump files are saved in a predetermined directory, which by default, is /var/crash/. In previous releases, crash dump files were overwritten when a system rebooted, unless you manually enabled the system to save the images of physical memory in a crash dump file. Now, the saving of crash dump files is enabled by default.

System crash information is managed with the dumpadm command. For more information, see Managing System Crash Dump Information With the dumpadm Command.

Saving Crash Dumps

You can examine the control structures, active tables, memory images of a live or crashed system kernel, and other information about the operation of the kernel by using the mdb utility. Using the mdb utility to its full potential requires a detailed knowledge of the kernel, and is beyond the scope of this manual. For information about using this utility, see the mdb(1) man page.

Managing System Crash Dump Information With the dumpadm Command

Use the dumpadm command to manage system crash dump information in the Oracle Solaris OS.

Dump configuration parameters are managed by the dumpadm command. The following table describes dumpadm's configuration parameters.

Dump Parameter
dump device
The device that stores dump data temporarily as the system crashes. When the dump device is not the swap area, savecore runs in the background, which speeds up the boot process.
savecore directory
The directory that stores system crash dump files.
dump content
Type of memory data to dump.
minimum free space
Minimum amount of free space required in the savecore directory after saving crash dump files. If no minimum free space has been configured, the default is one Mbyte.

For more information, see dumpadm(1M).

How the dumpadm Command Works

During system startup, the dumpadm command is invoked by the svc:/system/dumpadm:default service to configure crash dumps parameters.

Specifically, dumpadm initializes the dump device and the dump content through the /dev/dump interface.

After the dump configuration is complete, the savecore script looks for the location of the crash dump file directory. Then, savecore is invoked to check for crash dumps and check the content of the minfree file in the crash dump directory.