OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/kexec-tools?expand=0&rev=5

README.SUSE

@@ -151,6 +151,27 @@ Note that the available memory size for the recovery kernel is limited.
 Setting KDUMP_RUNLEVEL=5 (graphical login) is not recommended.
 
 
+Initrd-based Dump Saving
+========================
+
+The problem with the procedure mentioned above is that your root file
+system (or whatever partition your KDUMP_SAVEDIR is in) may be corrupted.
+So the script may not be able to mount the device and is not able to
+save your file to disk.
+
+For this, you can configure KDUMP_DUMPDEV to point to an unused partition
+that is large enough -- i.e. larger than the system's main memory -- to
+hold the dump. Before mounting the root file system, the init script
+writes the dump to that device. After rebooting, the normal boot script
+saves the dump from that device to KDUMP_SAVEDIR. Because the data was
+is saved to disk, you can safely turn off the computer and/or repair
+the file system using some tool (for example, you may need to boot from
+a CD which is no problem).
+
+After you changed that value, you have to re-run mkinitrd on the kdump
+kernel, or on all kernels.
+
+
 Tuning parameters
 =================
 
@@ -203,7 +224,8 @@ To enable network support in the Kdump recovery environment, set this to
 - KDUMP_IMMEDIATE_REBOOT
 
 This option specifies whether to reboot immediately after saving the
-core in the Kdump kernel. The default is "yes."
+core in the Kdump kernel. This option is ignored when KDUMP_DUMPDEV is
+set to a non-empty string. The default is "yes".
 
 
 - KDUMP_TRANSFER
@@ -234,7 +256,7 @@ If KDUMP_DUMPDEV points to a device file, the dump is written to that
 device when booting from the kdump kernel. The advantage over  is that
 you don't have to mount the root file system (which may be corrupted!)
 just to write the dump. On the first normal boot which is able to
-succesfully mount the root file system, the dump is saved to
+successfully mount the root file system, the dump is saved to
 KDUMP_SAVEDIR as usual.
 
 Important: The KDUMP_DUMPDEV is overwritten by kdump, so don't use it

kexec-tools.changes

@@ -1,3 +1,9 @@
+-------------------------------------------------------------------
+Thu Jan 25 19:28:57 CET 2007 - bwalle@suse.de
+
+- added documentation for initrd-based kdump saving
+- fixed description of KDUMP_IMMEDIATE_REBOOT
+
 -------------------------------------------------------------------
 Wed Jan 24 12:04:55 CET 2007 - tiwai@suse.de
 

kexec-tools.spec

@@ -19,7 +19,7 @@ Requires:       %insserv_prereq %fillup_prereq
 Autoreqprov:    on
 Summary:        Tools for fast kernel loading
 Version:        1.101
-Release:        65
+Release:        66
 Source:         %{name}-%{package_version}.tar.bz2
 Source1:        kdump
 Source2:        sysconfig.kdump
@@ -120,6 +120,9 @@ cd -
 %{_sbindir}/kdump-helper
 
 %changelog -n kexec-tools
+* Thu Jan 25 2007 - bwalle@suse.de
+- added documentation for initrd-based kdump saving
+- fixed description of KDUMP_IMMEDIATE_REBOOT
 * Wed Jan 24 2007 - tiwai@suse.de
 - fix invalid /proc/vmcore on ppc64 (#238078).
 * Thu Jan 18 2007 - bwalle@suse.de

sysconfig.kdump

@@ -52,7 +52,8 @@ KDUMP_RUNLEVEL="1"
 ## Default:	yes
 #
 # Immediately reboot after saving the core in the kdump kernel?
-# use "yes" or "no".  Default is "yes"
+# This option is ignored when KDUMP_DUMPDEV is set to a non-empty
+# value. Use "yes" or "no". Default is "yes".
 #
 KDUMP_IMMEDIATE_REBOOT="yes"
 
@@ -108,7 +109,7 @@ KDUMP_FREE_DISK_SIZE=64
 # If KDUMP_DUMPDEV points to a device file, the dump is written to that device
 # when booting from the kdump kernel. The advantage over  is that you don't have to
 # mount the root file system (which may be corrupted!) just to write the
-# dump. On the first normal boot which is able to succesfully mount the
+# dump. On the first normal boot which is able to successfully mount the
 # root file system, the dump is saved to KDUMP_SAVEDIR as usual.
 #
 # Important: The KDUMP_DUMPDEV is overwritten by kdump, so don't use it for