MINI SHELL

# In this file, '#' means a comment. So, any lines in this file that start
# with '#' are ignored, and are not written in an email.
# The following words are automatically replaced to appropriate words
# by diskdump service.
# - %MAILTO%
# - %FROM%
# - %CURRENT%
# - %NODENAME%
# - %RELEASE%
# - %MACHINE%
# - %DEVICE%
# - %CAUSE%
# - %DAYS%
# - %DUMPED_DATE%
#
To: %MAILTO%
From: %FROM%
Subject: [NOTICE] The memory dump still remains in the registered device.

----------------------------------------------
This email was sent by diskdump automatically.
Please do not reply directly to this email.
----------------------------------------------

As of %CURRENT%
In your system (%NODENAME%, %RELEASE%, %MACHINE%), the memory dump
still remains in %DEVICE% because %CAUSE% in /etc/sysconfig/diskdump
is enabled.
%DAYS% days have passed since the memory was dumped to %DEVICE%.
%DEVICE% won't be available to dump memory again because %DEVICE% is not
formatted.
If you would like to use %DEVICE% as a dump device, then please disable
%CAUSE% and restart diskdump service as soon as possible.
Note that diskdump won't work at all if the registered device is
only %DEVICE% that is not formatted.

According to "diskdumpfmt -cv %DEVICE%", the dumped date is %DUMPED_DATE%.

You can enable all of the registered device by the following command. 
  # service diskdump enabledevice

First, this disables both PRESERVEDUMP and SKIPSAVECORE temporarily. Then, this
could save panic dump, format the registered device, and restart diskdump
service without stopping.
Note that there must be the space enough to create dump file(s) in /var/crash
before you run the command.
PRESERVEDUMP works only if saving panic dump failed due to some error.
Consequently, you should investigate the cause and resolve the problem
before you run the command.