savecore

Before savecore writes out a core image, it reads a number from the file /etc/crash/minfree. If the number of free kilobytes in the filesystem after saving the core would be less than the number obtained from minfree, the core dump is not saved. If minfree does not exist, savecore always writes out the core file (assuming that a core dump was taken).

savecore is done in parallel with enabling services such as NFS. If a panic occurs prior to the completion of the savecore then the filer will do a synchronous savecore once it reboots.

-w

Starts savecore in a synchronous mode, which blocks other processing until the save has completed. Periodic progress updates will be displayed on the console.

-s

Displays the progress of the current savecore operation. If no save is in progress, but an unsaved core is present, a warning will be printed if the unsaved core cannot fit in the root filesystem.

-f

If savecore fails to save an unsaved core too many times, it will stop trying. This flag tells savecore to ignore the unsaved attempts, and try again. This attempt will be made synchronously.

-i

Displays information about the type of coredump that would be performed, if the system were to panic right now. If unsaved cores are present on the disks, this information will be included in the output.

-k

Invalidates the special core area that resides on each of the disks. Typically this is used when a savecore command cannot complete due to an error such as a disk read error.

-l

Lists all of the saved core files currently in the /etc/crash directory, along with the panic string, panic time, and OS version.

/etc/crash/core.*

saved core files

/etc/crash/bounds

suffix for next core file /etc/crash/minfree free KB in FS to maintain after savecore