blob: b064aa59714dba472d43562ecdeb6988c755d70e [file] [log] [blame]
Michael Holzheu7d4c7382014-04-14 11:56:07 +02001The s390 SCSI dump tool (zfcpdump)
Michael Holzheu411ed322007-04-27 16:01:49 +02002
3System z machines (z900 or higher) provide hardware support for creating system
4dumps on SCSI disks. The dump process is initiated by booting a dump tool, which
5has to create a dump of the current (probably crashed) Linux image. In order to
6not overwrite memory of the crashed Linux with data of the dump tool, the
Michael Holzheu7d4c7382014-04-14 11:56:07 +02007hardware saves some memory plus the register sets of the boot CPU before the
Michael Holzheu411ed322007-04-27 16:01:49 +02008dump tool is loaded. There exists an SCLP hardware interface to obtain the saved
9memory afterwards. Currently 32 MB are saved.
10
11This zfcpdump implementation consists of a Linux dump kernel together with
Michael Holzheu7d4c7382014-04-14 11:56:07 +020012a user space dump tool, which are loaded together into the saved memory region
Michael Holzheu411ed322007-04-27 16:01:49 +020013below 32 MB. zfcpdump is installed on a SCSI disk using zipl (as contained in
14the s390-tools package) to make the device bootable. The operator of a Linux
15system can then trigger a SCSI dump by booting the SCSI disk, where zfcpdump
16resides on.
17
Martin Schwidefskyffa52d02015-10-28 09:47:58 +010018The user space dump tool accesses the memory of the crashed system by means
19of the /proc/vmcore interface. This interface exports the crashed system's
20memory and registers in ELF core dump format. To access the memory which has
21been saved by the hardware SCLP requests will be created at the time the data
22is needed by /proc/vmcore. The tail part of the crashed systems memory which
23has not been stashed by hardware can just be copied from real memory.
Michael Holzheu411ed322007-04-27 16:01:49 +020024
Martin Schwidefskyffa52d02015-10-28 09:47:58 +010025To build a dump enabled kernel the kernel config option CONFIG_CRASH_DUMP
26has to be set.
Michael Holzheu411ed322007-04-27 16:01:49 +020027
Michael Holzheu7d4c7382014-04-14 11:56:07 +020028To get a valid zfcpdump kernel configuration use "make zfcpdump_defconfig".
Michael Holzheu411ed322007-04-27 16:01:49 +020029
Michael Holzheu7d4c7382014-04-14 11:56:07 +020030The s390 zipl tool looks for the zfcpdump kernel and optional initrd/initramfs
31under the following locations:
Michael Holzheu411ed322007-04-27 16:01:49 +020032
Michael Holzheu7d4c7382014-04-14 11:56:07 +020033* kernel: <zfcpdump directory>/zfcpdump.image
34* ramdisk: <zfcpdump directory>/zfcpdump.rd
Michael Holzheu411ed322007-04-27 16:01:49 +020035
Michael Holzheu7d4c7382014-04-14 11:56:07 +020036The zfcpdump directory is defined in the s390-tools package.
Michael Holzheu411ed322007-04-27 16:01:49 +020037
Michael Holzheu7d4c7382014-04-14 11:56:07 +020038The user space application of zfcpdump can reside in an intitramfs or an
39initrd. It can also be included in a built-in kernel initramfs. The application
40reads from /proc/vmcore or zcore/mem and writes the system dump to a SCSI disk.
Michael Holzheu411ed322007-04-27 16:01:49 +020041
Michael Holzheu7d4c7382014-04-14 11:56:07 +020042The s390-tools package version 1.24.0 and above builds an external zfcpdump
43initramfs with a user space application that writes the dump to a SCSI
44partition.
Michael Holzheu411ed322007-04-27 16:01:49 +020045
46For more information on how to use zfcpdump refer to the s390 'Using the Dump
47Tools book', which is available from
48http://www.ibm.com/developerworks/linux/linux390.