The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is invoked by the dumpadm service each time the system boots.
1. Check the error message information
<br /><br /># tail -f /var/adm/messages | grep savecore<br /><br />Oct 13 12:11:12 itsiti savecore: not enough space in<br /><br />/var/crash/itsiti (4567 MB avail, 5476 MB needed)<br /><br />
Additional note:
• From the error message, we know that the space is not enough in /var to save the crash dump.
2. Look for a available directory to save the crash dump as here we look onto /tmp for a temporary save
<br /><br /># df -h /tmp<br /><br />Filesystem Size Used Available Capacity Mounted on<br /><br />swap 70G 20K 50G 72% /tmp<br /><br />
Additional note:
• From the free available space, we will create a new directory to save the crash dump
3. Change directory to /tmp and create a temporary directory to save the crash dump.
<br /><br /># cd /tmp<br /><br /># mkdir crashdumptemp<br /><br /># cd crashdumptemp<br /><br />
4. Save the crash dump onto newly created directory.
<br /><br /># savecore -Ld /tmp/crashdumptemp<br /><br />dumping to .......<br /><br />100% done.....<br /><br />System dump time.....<br /><br />Constructing namelist....<br /><br />Constructing corefile....<br /><br />100% done....<br /><br />
Additional note:
• -L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way.
• -d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on the dump device indicates the dump has already been saved.
