Troubleshooting System Administration Issues in Oracle® Solaris 11.2

Exit Print View

Updated: September 2014
 
 

Modifying the Configuration for Crash Dumps

To modify the crash dump configuration, assume the root role and use the dumpadm command.

The syntax for the dumpadm command is as follows:

#  /usr/sbin/dumpadm [-nuy] [-c content-type] [-d dump-device] [-m mink | minm | min%]
[-s savecore-dir] [-r root-dir] [-z on | off]
–c content-type

Specifies the type of data to dump. The values for this option have changed for the Oracle Solaris 11.2 release. Use kernel to dump the kernel memory pages only, all to dump all memory pages, curproc, to dump kernel memory and the memory pages of the process whose thread was executing when the crash occurred, allproc, to dump kernal memory pages and all process pages, or zfs, to dump kernel pages which store ZFS metadata. The default dump content is kernel memory.

See the following examples of the –c option:

# dumpadm -c kernel
# dumpadm -c +zfs
# dumpadm -c -zfs
# dumpadm -c curproc+zfs
–d dump-device

Specifies the device that stores dump data temporarily when the system crashes. The primary dump device is the default dump device. When the dump device is not the swap area, savecore runs in the background, which speeds up the boot process.

–e

Prints estimate of disk space required for storing compressed crash dump. The value is computed using current configuration and currently running system.

–m mink | minm | min%

Specifies the minimum free disk space for saving crash dump files by creating a minfree file in the current savecore directory. This parameter can be specified in Kbytes (mink), Mbytes (minm) or file system size percentage (min%). If no minimum free space has been configured, the default is 1 Mbyte.

The savecore command consults this file prior to writing the crash dump files. If writing the crash dump files would decrease the amount of free space below the minfree threshold due to their size, the dump files are not written and an error message is logged. For information about recovering from this scenario, see Saving Data When the Crash Dump Directory is Full.

–n

Specifies that savecore should not be run when the system reboots. This dump configuration is not recommended. If system crash information is written to the swap device and savecore is not enabled, the crash dump information is overwritten when the system begins to swap.

–p

Produces machine-parsable output.

–s savecore-dir

Specifies an alternate directory for storing crash dump files. In Oracle Solaris 11, the default directory is /var/crash.

–u

Forcibly updates the kernel dump configuration based on the contents of the /etc/dumpadm.conf file.

–y

Modifies the dump configuration to automatically execute the savecore command upon reboot, which is the default for this dump setting.

–z on | off

Modifies the dump configuration to control the operation of the savecore command upon reboot. The on setting enables the saving of core file in a compressed format. The off setting automatically uncompresses the crash dump file. Because crash dump files can be extremely large and therefore require less file system space if they are saved in a compressed format, the default is on.

Example 1-1  Modifying a Crash Dump Configuration

In this example, all of memory is dumped to the dedicated dump device, /dev/zvol/dsk/rpool/dump, and the minimum free space that must be available after the crash dump files are saved is 10% of the file system space.

# dumpadm
      Dump content: kernel pages
       Dump device: /dev/zvol/dsk/rpool/dump (dedicated)
Savecore directory: /var/crash
  Savecore enabled: yes
   Save compressed: on

# dumpadm -c all -d /dev/zvol/dsk/rpool/dump -m 10%
       Dump content: all pages
       Dump device: /dev/zvol/dsk/rpool/dump (dedicated)
Savecore directory: /var/crash (minfree = 5697105KB)
  Savecore enabled: yes
   Save compressed: on