ERROR

This message occurs when there is an unsaved core on the dump device. The abort prevents a new crash from overwriting the original dump core, which is expected to contain more interesting information for analysis.

If the default behavior is not desired, then set the boot option 'save-latest-core?' to true.

Dump is aborted because a core in the dump device is not saved yet.

(None).

NOTICE

This message occurs once for each core disk that has read or write errors while dumping the core. Each disk is marked as failed, so further writes to the disks are dropped. Dumpcore tries to recover from this error, and continue dumping the core.

(None).

Disk %s had %u read and %u write error(s) during dumpcore.

disk (STRING): Name of this core disk marked failed with read or write errors.
readErrorCount (INT): Number of read errors seen on this core disk.
writeErrorCount (INT): Number of write errors seen on this core disk.

ERROR

During the last dumpcore attempt, disk write errors are ignored, and dumpcore continues. In this case, too many disks failed during the last dump attempt for savecore to create a core file. The core will be deleted, and no core will be available from this panic.

(None).

%d of %d disks failed during dumpcore

failed (INT): Number of failed disks
total (INT): Number of disks used

ERROR

This message occurs when the system fails to write a coredump due to lack of disk space.

Disk space needed for a coredump can be reduced by enabling sparse cores, which is the default setting. Verify that sparse cores are enabled by using the "system node coredump config show" command. If not, enable them by using the "system node coredump modify -node local -sparse-enabled true" command. If there is still not enough disk space to write a coredump, add a spare disk that is at least 0.6 times the sum of primary memory size and NVRAM memory size. You can obtain sizes of primary memory and NVRAM memory by using the "run local sysconfig" command and reading entries for system board and NVRAM.

Not enough disks to write core dump.

(None).

INFORMATIONAL

This message occurs when a core dump is not performed because the system was configured to not dump cores or dump is disabled in the code path that caused the system to panic. Any of the following configuration methods can disable coredump: - Environment variable "dont-dump-core?" is "true" - Parameter "-coredump-attempts" in the command "system node coredump config" is "0".

If the reason is "dump disabled in the current code path", there is no corrective action that can be taken. If the reason is "coredump configured to not dump cores", 1. "-coredump-attempts" parameter might be set to "0". Check the "Max Dump Attempts" value in the output of the "system node coredump config show -node node_name" command. If "0", use the "system node coredump config modify ←node node_name> -coredump-attempts <number_of_attempts>" command to set a non-zero value. The default is 2 attempts. 2. "dont-dump-core?" environment variable might be set to "true". From the nodeshell, use the (priv: diag) "bootargs dump" command to check whether "dont-dump-core?" exists and is set to "true". To unset the variable, use the "bootargs unset dont-dump-core?" command.

Coredump not performed because %s.

reason (STRING): Reason that coredump was not performed.

EMERGENCY

Coredump failed to complete.

Previously logged coredump.dump.* events should help explain the exact cause of the failure.

Dumpcore failed

(None).

ERROR

Unsaved cores occupy all the disks available to dumpcore.

Save the unsaved cores using "savecore" or "savecore -f". If the cores aren't needed, run "savecore -k" to delete them.

All available disks contain unsaved cores

(None).

ERROR

Could not find any suitable disks for dumping a core.

Make sure there are non-broken disks connected to (and owned by) the panicing host.

No valid disks found

(None).

ERROR

A sparecore dump is supposed to be done, but no suitable spare disk can be found. In these situations, it is more important to allow a fast takeover than it is to get the core, so the dump is terminated, and takeover begins.

Add a spare disk to the system, or disable the "cf.takeover.on_panic" option.

No valid spare disk found

(None).

ERROR

Error while copying NVRAM into main memory during dumpcore. The resulting coredump will have dummy data in the NVRAM segment.

(None).

Error while copying NVRAM contents into main memory

(None).

ERROR

RAID has not yet processed the labels on the, disks, so dumpcore cannot proceed. This is typically the case for panics very early during boot.

(None).

RAID not ready to dump cores

(None).

ERROR

A recursive panic situation has been encountered. The location of the second panic makes it unsafe to attempt another dump.

(None).

Late recursive panic caused dumpcore to abort

(None).

ERROR

The boot option save-latest-core? is set to true. This will discard all unsaved cores during coredump.

If the behavior is not desired then set the boot option save-latest-core? to false.

Saving the latest core and discarding all unsaved cores.

(None).

NOTICE

This message occurs when the coredump process was asked to scrub sensitive memory areas but could not do so. The dump must be aborted to avoid saving such memory areas to disk.

(None).

Could not scrub protected memory regions.

(None).

ERROR

Dumpcore ran out of space for the core segments in the header. This core cannot be dumped.

Disable the "coredump.metadata_only" option.

Out of segment space in the core header

(None).

ERROR

The selected spare disk might not be big enough to hold the core. The dump attempt has been aborted.

Make sure a spare disk is available that is at least as big as the sum of main memory and NVRAM. Set the option "coredump.metadata_only" to "on". If the problem persists, turn off the option "cf.takeover.on_panic". This will disable the sparecore feature, and delay takeovers until the panicing partner has finished dumping the core.

Spare disk too small for coredump

(None).

INFORMATIONAL

Basic info about start of dumpcore

(None).

%s starting with %d disks

type (STRING): Type of dump. Possible types are compressed, sprayed, and sparecore.
disks (INT): Number of disks being used

INFORMATIONAL

Information about how long dumpcore took to complete.

(None).

%s completed in %d seconds

type (STRING): Type of dump. Possible types are compressed, sprayed, and sparecore.
seconds (INT): Number of seconds spent on the dump

ERROR

Failed to write dump data blocks to disk. If the write failed because of disk problems, dumpcore will restart, without the disk that failed. If the write failed for other reasons (eg. attempt to write to a bad position on the disk), dumpcore will be aborted.

(None).

Error dumping %llu blocks starting at block %llu to disk %s

blocks (LONGINT): Number of blocks trying to be dumped
start (LONGINT): Starting block number
disk (STRING): Name of disk on which the write failed

ERROR

An i/o error occurred while attempting to write a coredump to disk.

(None).

An i/o error occurred while attempting to dump core.

(None).

ERROR

Failed to write the core header to disk during dumpcore.

(None).

Error writing core header to block %llu on disk %s

header (LONGINT): Block number of the core header block
disk (STRING): Name of disk on which the write failed