Toshaan Bharvani
2 years ago
commit
69dd3add4d
46 changed files with 11492 additions and 0 deletions
@ -0,0 +1,36 @@
@@ -0,0 +1,36 @@
|
||||
#!/usr/bin/bash |
||||
|
||||
COMMAND="$1" |
||||
KERNEL_VERSION="$2" |
||||
KDUMP_INITRD_DIR_ABS="$3" |
||||
KERNEL_IMAGE="$4" |
||||
|
||||
if ! [[ ${KERNEL_INSTALL_MACHINE_ID-x} ]]; then |
||||
exit 0 |
||||
fi |
||||
|
||||
if [[ -d "$KDUMP_INITRD_DIR_ABS" ]]; then |
||||
KDUMP_INITRD="initrdkdump" |
||||
else |
||||
# If `KDUMP_BOOTDIR` is not writable, then the kdump |
||||
# initrd must have been placed at `/var/lib/kdump` |
||||
if [[ ! -w "/boot" ]]; then |
||||
KDUMP_INITRD_DIR_ABS="/var/lib/kdump" |
||||
else |
||||
KDUMP_INITRD_DIR_ABS="/boot" |
||||
fi |
||||
KDUMP_INITRD="initramfs-${KERNEL_VERSION}kdump.img" |
||||
fi |
||||
|
||||
ret=0 |
||||
case "$COMMAND" in |
||||
add) |
||||
# Do nothing, kdump initramfs is strictly host only |
||||
# and managed by kdump service |
||||
;; |
||||
remove) |
||||
rm -f -- "$KDUMP_INITRD_DIR_ABS/$KDUMP_INITRD" |
||||
ret=$? |
||||
;; |
||||
esac |
||||
exit $ret |
||||
@ -0,0 +1,13 @@
@@ -0,0 +1,13 @@
|
||||
#!/usr/bin/bash |
||||
|
||||
COMMAND="$1" |
||||
KERNEL_VERSION="$2" |
||||
KDUMP_INITRD_DIR_ABS="$3" |
||||
KERNEL_IMAGE="$4" |
||||
|
||||
case "$COMMAND" in |
||||
add) |
||||
kdumpctl reset-crashkernel-for-installed_kernel "$KERNEL_VERSION" |
||||
exit 0 |
||||
;; |
||||
esac |
||||
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
SUBSYSTEM=="cpu", ACTION=="add", GOTO="kdump_reload" |
||||
SUBSYSTEM=="cpu", ACTION=="remove", GOTO="kdump_reload" |
||||
SUBSYSTEM=="memory", ACTION=="online", GOTO="kdump_reload" |
||||
SUBSYSTEM=="memory", ACTION=="offline", GOTO="kdump_reload" |
||||
|
||||
GOTO="kdump_reload_end" |
||||
|
||||
LABEL="kdump_reload" |
||||
|
||||
# If kdump is not loaded, calling kdump-udev-throttle will end up |
||||
# doing nothing, but systemd-run will always generate extra logs for |
||||
# each call, so trigger the kdump-udev-throttler only if kdump |
||||
# service is active to avoid unnecessary logs |
||||
RUN+="/bin/sh -c '/usr/bin/systemctl is-active kdump.service || exit 0; /usr/bin/systemd-run --quiet --no-block /usr/lib/udev/kdump-udev-throttler'" |
||||
|
||||
LABEL="kdump_reload_end" |
||||
@ -0,0 +1,22 @@
@@ -0,0 +1,22 @@
|
||||
SUBSYSTEM=="cpu", ACTION=="online", GOTO="kdump_reload_cpu" |
||||
SUBSYSTEM=="memory", ACTION=="online", GOTO="kdump_reload_mem" |
||||
SUBSYSTEM=="memory", ACTION=="offline", GOTO="kdump_reload_mem" |
||||
|
||||
GOTO="kdump_reload_end" |
||||
|
||||
# If kdump is not loaded, calling kdump-udev-throttle will end up |
||||
# doing nothing, but systemd-run will always generate extra logs for |
||||
# each call, so trigger the kdump-udev-throttler only if kdump |
||||
# service is active to avoid unnecessary logs |
||||
|
||||
LABEL="kdump_reload_mem" |
||||
|
||||
RUN+="/bin/sh -c '/usr/bin/systemctl is-active kdump.service || exit 0; /usr/bin/systemd-run --quiet --no-block /usr/lib/udev/kdump-udev-throttler'" |
||||
|
||||
GOTO="kdump_reload_end" |
||||
|
||||
LABEL="kdump_reload_cpu" |
||||
|
||||
RUN+="/bin/sh -c '/usr/bin/systemctl is-active kdump.service || exit 0; ! test -f /sys/kernel/fadump_enabled || cat /sys/kernel/fadump_enabled | grep 0 || exit 0; /usr/bin/systemd-run --quiet --no-block /usr/lib/udev/kdump-udev-throttler'" |
||||
|
||||
LABEL="kdump_reload_end" |
||||
@ -0,0 +1,119 @@
@@ -0,0 +1,119 @@
|
||||
Introduction |
||||
============ |
||||
|
||||
This document describes features the kexec-tools package provides for setting |
||||
and estimating the crashkernel value. |
||||
|
||||
Kdump lives in a pre-reserved chunk of memory, and the size of the reserved |
||||
memory is specified by the `crashkernel=` kernel parameter. It's hard to |
||||
estimate an accurate `crashkernel=` value, so it's always recommended to test |
||||
kdump after you updated the `crashkernel=` value or changed the dump target. |
||||
|
||||
|
||||
Default crashkernel value |
||||
========================= |
||||
|
||||
Latest kexec-tools provides "kdumpctl get-default-crashkernel" to retrieve |
||||
the default crashkernel value, |
||||
|
||||
$ echo $(kdumpctl get-default-crashkernel) |
||||
1G-4G:192M,4G-64G:256M,64G-102400T:512M |
||||
|
||||
It will be taken as the default value of 'crashkernel=', you can use |
||||
this value as a reference for setting crashkernel value manually. |
||||
|
||||
|
||||
New installed system |
||||
==================== |
||||
|
||||
Anaconda is the OS installer which sets all the kernel boot cmdline on a newly |
||||
installed system. If kdump is enabled during Anaconda installation, Anaconda |
||||
will use the default crashkernel value as the default `crashkernel=` value on |
||||
the newly installed system. |
||||
|
||||
Users can override the value during Anaconda installation manually. |
||||
|
||||
|
||||
Auto update of crashkernel boot parameter |
||||
========================================= |
||||
|
||||
A new release of kexec-tools could update the default crashkernel value. |
||||
By default, kexec-tools would reset crashkernel to the new default value if it |
||||
detects old default crashkernel value is used by installed kernels. If you don't |
||||
want kexec-tools to update the old default crashkernel to the new default |
||||
crashkernel, you can change auto_reset_crashkernel to no in kdump.conf. |
||||
|
||||
Supported Bootloaders |
||||
--------------------- |
||||
|
||||
This auto update only works with GRUB2 and ZIPL, as kexec-tools heavily depends |
||||
on `grubby`. If other boot loaders are used, the user will have to update the |
||||
`crashkernel=` value manually. |
||||
|
||||
|
||||
Reset crashkernel to default value |
||||
================================== |
||||
|
||||
kexec-tools only perform the auto update of crashkernel value when it can |
||||
confirm the boot kernel's crashkernel value is using its corresponding default |
||||
value and auto_reset_crashkernel=yes in kdump.conf. In other cases, the user |
||||
can reset the crashkernel value by themselves. |
||||
|
||||
Reset using kdumpctl |
||||
-------------------- |
||||
|
||||
To make it easier to reset the `crashkernel=` kernel cmdline to this default |
||||
value properly, `kdumpctl` also provides a sub-command: |
||||
|
||||
`kdumpctl reset-crashkernel [--kernel=path_to_kernel] [--reboot]` |
||||
|
||||
This command will read from the `crashkernel.default` file and reset |
||||
bootloader's kernel cmdline to the default value. It will also update bootloader |
||||
config if the bootloader has a standalone config file. User will have to reboot |
||||
the machine after this command to make it take effect if --reboot is not specified. |
||||
For ppc64le, an optional "[--fadump=[on|off|nocma]]" can also be specified to toggle |
||||
FADump on/off. |
||||
|
||||
Reset manually |
||||
-------------- |
||||
|
||||
To reset the crashkernel value manually, it's recommended to use utils like |
||||
`grubby`. A one liner script for resetting `crashkernel=` value of all installed |
||||
kernels to current boot kernel's crashkernel.default` is: |
||||
|
||||
grubby --update-kernel ALL --args "crashkernel=$(kdumpctl get-default-crashkernel)" |
||||
|
||||
Estimate crashkernel |
||||
==================== |
||||
|
||||
The best way to estimate a usable crashkernel value is by testing kdump |
||||
manually. And you can set crashkernel to a large value, then adjust the |
||||
crashkernel value to an acceptable value gradually. |
||||
|
||||
`kdumpctl` also provides a sub-command for doing rough estimating without |
||||
triggering kdump: |
||||
|
||||
`kdumpctl estimate` |
||||
|
||||
The output will be like this: |
||||
|
||||
``` |
||||
Encrypted kdump target requires extra memory, assuming using the keyslot with minimun memory requirement |
||||
|
||||
Reserved crashkernel: 256M |
||||
Recommended crashkernel: 655M |
||||
|
||||
Kernel image size: 47M |
||||
Kernel modules size: 12M |
||||
Initramfs size: 19M |
||||
Runtime reservation: 64M |
||||
LUKS required size: 512M |
||||
Large modules: |
||||
xfs: 1892352 |
||||
nouveau: 2318336 |
||||
WARNING: Current crashkernel size is lower than recommended size 655M. |
||||
``` |
||||
|
||||
It will generate a summary report about the estimated memory consumption |
||||
of each component of kdump. The value may not be accurate enough, but |
||||
would be a good start for finding a suitable crashkernel value. |
||||
@ -0,0 +1,65 @@
@@ -0,0 +1,65 @@
|
||||
#!/bin/bash |
||||
|
||||
. /etc/sysconfig/kdump |
||||
|
||||
KDUMP_KERNEL="" |
||||
KDUMP_INITRD="" |
||||
|
||||
check() { |
||||
if [[ ! -f /etc/sysconfig/kdump ]] || [[ ! -f /lib/kdump/kdump-lib.sh ]] \ |
||||
|| [[ -n ${IN_KDUMP} ]]; then |
||||
return 1 |
||||
fi |
||||
return 255 |
||||
} |
||||
|
||||
depends() { |
||||
echo "base shutdown" |
||||
return 0 |
||||
} |
||||
|
||||
prepare_kernel_initrd() { |
||||
. /lib/kdump/kdump-lib.sh |
||||
|
||||
prepare_kdump_bootinfo |
||||
|
||||
# $kernel is a variable from dracut |
||||
if [[ $KDUMP_KERNELVER != "$kernel" ]]; then |
||||
dwarn "Using kernel version '$KDUMP_KERNELVER' for early kdump," \ |
||||
"but the initramfs is generated for kernel version '$kernel'" |
||||
fi |
||||
} |
||||
|
||||
install() { |
||||
prepare_kernel_initrd |
||||
if [[ ! -f $KDUMP_KERNEL ]]; then |
||||
derror "Could not find required kernel for earlykdump," \ |
||||
"earlykdump will not work!" |
||||
return 1 |
||||
fi |
||||
if [[ ! -f $KDUMP_INITRD ]]; then |
||||
derror "Could not find required kdump initramfs for earlykdump," \ |
||||
"please ensure kdump initramfs is generated first," \ |
||||
"earlykdump will not work!" |
||||
return 1 |
||||
fi |
||||
|
||||
inst_multiple tail find cut dirname hexdump |
||||
inst_simple "/etc/sysconfig/kdump" |
||||
inst_binary "/usr/sbin/kexec" |
||||
inst_binary "/usr/bin/gawk" "/usr/bin/awk" |
||||
inst_binary "/usr/bin/logger" "/usr/bin/logger" |
||||
inst_binary "/usr/bin/printf" "/usr/bin/printf" |
||||
inst_binary "/usr/bin/xargs" "/usr/bin/xargs" |
||||
inst_script "/lib/kdump/kdump-lib.sh" "/lib/kdump-lib.sh" |
||||
inst_script "/lib/kdump/kdump-lib-initramfs.sh" "/lib/kdump/kdump-lib-initramfs.sh" |
||||
inst_script "/lib/kdump/kdump-logger.sh" "/lib/kdump-logger.sh" |
||||
inst_hook cmdline 00 "$moddir/early-kdump.sh" |
||||
inst_binary "$KDUMP_KERNEL" |
||||
inst_binary "$KDUMP_INITRD" |
||||
|
||||
ln_r "$KDUMP_KERNEL" "/boot/kernel-earlykdump" |
||||
ln_r "$KDUMP_INITRD" "/boot/initramfs-earlykdump" |
||||
|
||||
chmod -x "${initdir}/$KDUMP_KERNEL" |
||||
} |
||||
@ -0,0 +1,84 @@
@@ -0,0 +1,84 @@
|
||||
#! /bin/sh |
||||
|
||||
KEXEC=/sbin/kexec |
||||
standard_kexec_args="-p" |
||||
|
||||
EARLY_KDUMP_INITRD="" |
||||
EARLY_KDUMP_KERNEL="" |
||||
EARLY_KDUMP_CMDLINE="" |
||||
EARLY_KDUMP_KERNELVER="" |
||||
EARLY_KEXEC_ARGS="" |
||||
|
||||
. /etc/sysconfig/kdump |
||||
. /lib/dracut-lib.sh |
||||
. /lib/kdump-lib.sh |
||||
. /lib/kdump-logger.sh |
||||
|
||||
# initiate the kdump logger |
||||
if ! dlog_init; then |
||||
echo "failed to initiate the kdump logger." |
||||
exit 1 |
||||
fi |
||||
|
||||
prepare_parameters() |
||||
{ |
||||
EARLY_KDUMP_CMDLINE=$(prepare_cmdline "${KDUMP_COMMANDLINE}" "${KDUMP_COMMANDLINE_REMOVE}" "${KDUMP_COMMANDLINE_APPEND}") |
||||
EARLY_KDUMP_KERNEL="/boot/kernel-earlykdump" |
||||
EARLY_KDUMP_INITRD="/boot/initramfs-earlykdump" |
||||
} |
||||
|
||||
early_kdump_load() |
||||
{ |
||||
if ! check_kdump_feasibility; then |
||||
return 1 |
||||
fi |
||||
|
||||
if is_fadump_capable; then |
||||
dwarn "WARNING: early kdump doesn't support fadump." |
||||
return 1 |
||||
fi |
||||
|
||||
if check_current_kdump_status; then |
||||
return 1 |
||||
fi |
||||
|
||||
prepare_parameters |
||||
|
||||
EARLY_KEXEC_ARGS=$(prepare_kexec_args "${KEXEC_ARGS}") |
||||
|
||||
if is_secure_boot_enforced; then |
||||
dinfo "Secure Boot is enabled. Using kexec file based syscall." |
||||
EARLY_KEXEC_ARGS="$EARLY_KEXEC_ARGS -s" |
||||
fi |
||||
|
||||
# Here, only output the messages, but do not save these messages |
||||
# to a file because the target disk may not be mounted yet, the |
||||
# earlykdump is too early. |
||||
ddebug "earlykdump: $KEXEC ${EARLY_KEXEC_ARGS} $standard_kexec_args \ |
||||
--command-line=$EARLY_KDUMP_CMDLINE --initrd=$EARLY_KDUMP_INITRD \ |
||||
$EARLY_KDUMP_KERNEL" |
||||
|
||||
if $KEXEC $EARLY_KEXEC_ARGS $standard_kexec_args \ |
||||
--command-line="$EARLY_KDUMP_CMDLINE" \ |
||||
--initrd=$EARLY_KDUMP_INITRD $EARLY_KDUMP_KERNEL; then |
||||
dinfo "kexec: loaded early-kdump kernel" |
||||
return 0 |
||||
else |
||||
derror "kexec: failed to load early-kdump kernel" |
||||
return 1 |
||||
fi |
||||
} |
||||
|
||||
set_early_kdump() |
||||
{ |
||||
if getargbool 0 rd.earlykdump; then |
||||
dinfo "early-kdump is enabled." |
||||
early_kdump_load |
||||
else |
||||
dinfo "early-kdump is disabled." |
||||
fi |
||||
|
||||
return 0 |
||||
} |
||||
|
||||
set_early_kdump |
||||
@ -0,0 +1,48 @@
@@ -0,0 +1,48 @@
|
||||
#!/bin/sh |
||||
export PATH=/usr/bin:/usr/sbin |
||||
export SYSTEMD_IN_INITRD=lenient |
||||
|
||||
[ -e /proc/mounts ] || |
||||
(mkdir -p /proc && mount -t proc -o nosuid,noexec,nodev proc /proc) |
||||
|
||||
grep -q '^sysfs /sys sysfs' /proc/mounts || |
||||
(mkdir -p /sys && mount -t sysfs -o nosuid,noexec,nodev sysfs /sys) |
||||
|
||||
grep -q '^none / ' /proc/mounts || grep -q '^rootfs / ' /proc/mounts && ROOTFS_IS_RAMFS=1 |
||||
|
||||
if [ -f /proc/device-tree/rtas/ibm,kernel-dump ] || [ -f /proc/device-tree/ibm,opal/dump/mpipl-boot ]; then |
||||
mkdir /newroot |
||||
mount -t ramfs ramfs /newroot |
||||
|
||||
if [ $ROOTFS_IS_RAMFS ]; then |
||||
for FILE in $(ls -A /fadumproot/); do |
||||
mv /fadumproot/$FILE /newroot/ |
||||
done |
||||
exec switch_root /newroot /init |
||||
else |
||||
mkdir /newroot/sys /newroot/proc /newroot/dev /newroot/run /newroot/oldroot |
||||
|
||||
grep -q '^devtmpfs /dev devtmpfs' /proc/mounts && mount --move /dev /newroot/dev |
||||
grep -q '^tmpfs /run tmpfs' /proc/mounts && mount --move /run /newroot/run |
||||
mount --move /sys /newroot/sys |
||||
mount --move /proc /newroot/proc |
||||
|
||||
cp --reflink=auto --sparse=auto --preserve=mode,timestamps,links -dfr /fadumproot/. /newroot/ |
||||
cd /newroot && pivot_root . oldroot |
||||
|
||||
loop=1 |
||||
while [ $loop ]; do |
||||
unset loop |
||||
while read -r _ mp _; do |
||||
case $mp in |
||||
/oldroot/*) umount -d "$mp" && loop=1 ;; |
||||
esac |
||||
done </proc/mounts |
||||
done |
||||
umount -d -l oldroot |
||||
|
||||
exec /init |
||||
fi |
||||
else |
||||
exec /init.dracut |
||||
fi |
||||
@ -0,0 +1,23 @@
@@ -0,0 +1,23 @@
|
||||
#!/bin/bash |
||||
|
||||
check() { |
||||
return 255 |
||||
} |
||||
|
||||
depends() { |
||||
return 0 |
||||
} |
||||
|
||||
install() { |
||||
mv -f "$initdir/init" "$initdir/init.dracut" |
||||
inst_script "$moddir/init-fadump.sh" /init |
||||
chmod a+x "$initdir/init" |
||||
|
||||
# Install required binaries for the init script (init-fadump.sh) |
||||
inst_multiple sh modprobe grep mkdir mount |
||||
if dracut_module_included "squash"; then |
||||
inst_multiple cp pivot_root umount |
||||
else |
||||
inst_multiple ls mv switch_root |
||||
fi |
||||
} |
||||
@ -0,0 +1,30 @@
@@ -0,0 +1,30 @@
|
||||
# This file is part of systemd. |
||||
# |
||||
# systemd is free software; you can redistribute it and/or modify it |
||||
# under the terms of the GNU Lesser General Public License as published by |
||||
# the Free Software Foundation; either version 2.1 of the License, or |
||||
# (at your option) any later version. |
||||
|
||||
[Unit] |
||||
Description=Kdump Vmcore Save Service |
||||
After=initrd.target initrd-parse-etc.service sysroot.mount |
||||
After=dracut-initqueue.service dracut-pre-mount.service dracut-mount.service dracut-pre-pivot.service |
||||
Before=initrd-cleanup.service |
||||
ConditionPathExists=/etc/initrd-release |
||||
OnFailure=emergency.target |
||||
OnFailureJobMode=isolate |
||||
|
||||
[Service] |
||||
Environment=DRACUT_SYSTEMD=1 |
||||
Environment=NEWROOT=/sysroot |
||||
Type=oneshot |
||||
ExecStart=/bin/kdump.sh |
||||
StandardInput=null |
||||
StandardOutput=syslog |
||||
StandardError=syslog+console |
||||
KillMode=process |
||||
RemainAfterExit=yes |
||||
|
||||
# Bash ignores SIGTERM, so we send SIGHUP instead, to ensure that bash |
||||
# terminates cleanly. |
||||
KillSignal=SIGHUP |
||||
@ -0,0 +1,27 @@
@@ -0,0 +1,27 @@
|
||||
# This service will run the real kdump error handler code. Executing the |
||||
# failure action configured in kdump.conf |
||||
|
||||
[Unit] |
||||
Description=Kdump Error Handler |
||||
DefaultDependencies=no |
||||
After=systemd-vconsole-setup.service |
||||
Wants=systemd-vconsole-setup.service |
||||
|
||||
[Service] |
||||
Environment=HOME=/ |
||||
Environment=DRACUT_SYSTEMD=1 |
||||
Environment=NEWROOT=/sysroot |
||||
WorkingDirectory=/ |
||||
ExecStart=/bin/kdump.sh --error-handler |
||||
ExecStopPost=-/bin/rm -f -- /.console_lock |
||||
Type=oneshot |
||||
StandardInput=tty-force |
||||
StandardOutput=inherit |
||||
StandardError=inherit |
||||
KillMode=process |
||||
IgnoreSIGPIPE=no |
||||
TasksMax=infinity |
||||
|
||||
# Bash ignores SIGTERM, so we send SIGHUP instead, to ensure that bash |
||||
# terminates cleanly. |
||||
KillSignal=SIGHUP |
||||
@ -0,0 +1,14 @@
@@ -0,0 +1,14 @@
|
||||
# This file is part of systemd. |
||||
# |
||||
# systemd is free software; you can redistribute it and/or modify it |
||||
# under the terms of the GNU Lesser General Public License as published by |
||||
# the Free Software Foundation; either version 2.1 of the License, or |
||||
# (at your option) any later version. |
||||
|
||||
[Unit] |
||||
Description=Emergency Mode |
||||
Documentation=man:systemd.special(7) |
||||
Requires=emergency.service |
||||
After=emergency.service |
||||
AllowIsolate=yes |
||||
IgnoreOnIsolate=yes |
||||
@ -0,0 +1,583 @@
@@ -0,0 +1,583 @@
|
||||
#!/bin/sh |
||||
# |
||||
# The main kdump routine in capture kernel, bash may not be the |
||||
# default shell. Any code added must be POSIX compliant. |
||||
|
||||
. /lib/dracut-lib.sh |
||||
. /lib/kdump-logger.sh |
||||
. /lib/kdump-lib-initramfs.sh |
||||
|
||||
#initiate the kdump logger |
||||
if ! dlog_init; then |
||||
echo "failed to initiate the kdump logger." |
||||
exit 1 |
||||
fi |
||||
|
||||
KDUMP_PATH="/var/crash" |
||||
KDUMP_LOG_FILE="/run/initramfs/kexec-dmesg.log" |
||||
CORE_COLLECTOR="" |
||||
DEFAULT_CORE_COLLECTOR="makedumpfile -l --message-level 7 -d 31" |
||||
DMESG_COLLECTOR="/sbin/vmcore-dmesg" |
||||
FAILURE_ACTION="systemctl reboot -f" |
||||
DATEDIR=$(date +%Y-%m-%d-%T) |
||||
HOST_IP='127.0.0.1' |
||||
DUMP_INSTRUCTION="" |
||||
SSH_KEY_LOCATION="/root/.ssh/kdump_id_rsa" |
||||
DD_BLKSIZE=512 |
||||
FINAL_ACTION="systemctl reboot -f" |
||||
KDUMP_PRE="" |
||||
KDUMP_POST="" |
||||
NEWROOT="/sysroot" |
||||
OPALCORE="/sys/firmware/opal/mpipl/core" |
||||
KDUMP_CONF_PARSED="/tmp/kdump.conf.$$" |
||||
|
||||
# POSIX doesn't have pipefail, only apply when using bash |
||||
# shellcheck disable=SC3040 |
||||
[ -n "$BASH" ] && set -o pipefail |
||||
|
||||
DUMP_RETVAL=0 |
||||
|
||||
kdump_read_conf > $KDUMP_CONF_PARSED |
||||
|
||||
get_kdump_confs() |
||||
{ |
||||
while read -r config_opt config_val; do |
||||
# remove inline comments after the end of a directive. |
||||
case "$config_opt" in |
||||
path) |
||||
KDUMP_PATH="$config_val" |
||||
;; |
||||
core_collector) |
||||
[ -n "$config_val" ] && CORE_COLLECTOR="$config_val" |
||||
;; |
||||
sshkey) |
||||
if [ -f "$config_val" ]; then |
||||
SSH_KEY_LOCATION=$config_val |
||||
fi |
||||
;; |
||||
kdump_pre) |
||||
KDUMP_PRE="$config_val" |
||||
;; |
||||
kdump_post) |
||||
KDUMP_POST="$config_val" |
||||
;; |
||||
fence_kdump_args) |
||||
FENCE_KDUMP_ARGS="$config_val" |
||||
;; |
||||
fence_kdump_nodes) |
||||
FENCE_KDUMP_NODES="$config_val" |
||||
;; |
||||
failure_action | default) |
||||
case $config_val in |
||||
shell) |
||||
FAILURE_ACTION="kdump_emergency_shell" |
||||
;; |
||||
reboot) |
||||
FAILURE_ACTION="systemctl reboot -f && exit" |
||||
;; |
||||
halt) |
||||
FAILURE_ACTION="halt && exit" |
||||
;; |
||||
poweroff) |
||||
FAILURE_ACTION="systemctl poweroff -f && exit" |
||||
;; |
||||
dump_to_rootfs) |
||||
FAILURE_ACTION="dump_to_rootfs" |
||||
;; |
||||
esac |
||||
;; |
||||
final_action) |
||||
case $config_val in |
||||
reboot) |
||||
FINAL_ACTION="systemctl reboot -f" |
||||
;; |
||||
halt) |
||||
FINAL_ACTION="halt" |
||||
;; |
||||
poweroff) |
||||
FINAL_ACTION="systemctl poweroff -f" |
||||
;; |
||||
esac |
||||
;; |
||||
esac |
||||
done < "$KDUMP_CONF_PARSED" |
||||
|
||||
if [ -z "$CORE_COLLECTOR" ]; then |
||||
CORE_COLLECTOR="$DEFAULT_CORE_COLLECTOR" |
||||
if is_ssh_dump_target || is_raw_dump_target; then |
||||
CORE_COLLECTOR="$CORE_COLLECTOR -F" |
||||
fi |
||||
fi |
||||
} |
||||
|
||||
# store the kexec kernel log to a file. |
||||
save_log() |
||||
{ |
||||
dmesg -T > $KDUMP_LOG_FILE |
||||
|
||||
if command -v journalctl > /dev/null; then |
||||
journalctl -ab >> $KDUMP_LOG_FILE |
||||
fi |
||||
chmod 600 $KDUMP_LOG_FILE |
||||
} |
||||
|
||||
# $1: dump path, must be a mount point |
||||
dump_fs() |
||||
{ |
||||
ddebug "dump_fs _mp=$1" |
||||
|
||||
if ! is_mounted "$1"; then |
||||
dinfo "dump path '$1' is not mounted, trying to mount..." |
||||
if ! mount --target "$1"; then |
||||
derror "failed to dump to '$1', it's not a mount point!" |
||||
return 1 |
||||
fi |
||||
fi |
||||
|
||||
# Remove -F in makedumpfile case. We don't want a flat format dump here. |
||||
case $CORE_COLLECTOR in |
||||
*makedumpfile*) |
||||
CORE_COLLECTOR=$(echo "$CORE_COLLECTOR" | sed -e "s/-F//g") |
||||
;; |
||||
esac |
||||
|
||||
_dump_fs_path=$(echo "$1/$KDUMP_PATH/$HOST_IP-$DATEDIR/" | tr -s /) |
||||
dinfo "saving to $_dump_fs_path" |
||||
|
||||
# Only remount to read-write mode if the dump target is mounted read-only. |
||||
_dump_mnt_op=$(get_mount_info OPTIONS target "$1" -f) |
||||
case $_dump_mnt_op in |
||||
ro*) |
||||
dinfo "Remounting the dump target in rw mode." |
||||
mount -o remount,rw "$1" || return 1 |
||||
;; |
||||
esac |
||||
|
||||
mkdir -p "$_dump_fs_path" || return 1 |
||||
|
||||
save_vmcore_dmesg_fs ${DMESG_COLLECTOR} "$_dump_fs_path" |
||||
save_opalcore_fs "$_dump_fs_path" |
||||
|
||||
dinfo "saving vmcore" |
||||
$CORE_COLLECTOR /proc/vmcore "$_dump_fs_path/vmcore-incomplete" |
||||
_dump_exitcode=$? |
||||
if [ $_dump_exitcode -eq 0 ]; then |
||||
mv "$_dump_fs_path/vmcore-incomplete" "$_dump_fs_path/vmcore" |
||||
sync |
||||
dinfo "saving vmcore complete" |
||||
else |
||||
derror "saving vmcore failed, exitcode:$_dump_exitcode" |
||||
fi |
||||
|
||||
dinfo "saving the $KDUMP_LOG_FILE to $_dump_fs_path/" |
||||
save_log |
||||
mv "$KDUMP_LOG_FILE" "$_dump_fs_path/" |
||||
if [ $_dump_exitcode -ne 0 ]; then |
||||
return 1 |
||||
fi |
||||
|
||||
# improper kernel cmdline can cause the failure of echo, we can ignore this kind of failure |
||||
return 0 |
||||
} |
||||
|
||||
# $1: dmesg collector |
||||
# $2: dump path |
||||
save_vmcore_dmesg_fs() |
||||
{ |
||||
dinfo "saving vmcore-dmesg.txt to $2" |
||||
if $1 /proc/vmcore > "$2/vmcore-dmesg-incomplete.txt"; then |
||||
mv "$2/vmcore-dmesg-incomplete.txt" "$2/vmcore-dmesg.txt" |
||||
chmod 600 "$2/vmcore-dmesg.txt" |
||||
|
||||
# Make sure file is on disk. There have been instances where later |
||||
# saving vmcore failed and system rebooted without sync and there |
||||
# was no vmcore-dmesg.txt available. |
||||
sync |
||||
dinfo "saving vmcore-dmesg.txt complete" |
||||
else |
||||
if [ -f "$2/vmcore-dmesg-incomplete.txt" ]; then |
||||
chmod 600 "$2/vmcore-dmesg-incomplete.txt" |
||||
fi |
||||
derror "saving vmcore-dmesg.txt failed" |
||||
fi |
||||
} |
||||
|
||||
# $1: dump path |
||||
save_opalcore_fs() |
||||
{ |
||||
if [ ! -f $OPALCORE ]; then |
||||
# Check if we are on an old kernel that uses a different path |
||||
if [ -f /sys/firmware/opal/core ]; then |
||||
OPALCORE="/sys/firmware/opal/core" |
||||
else |
||||
return 0 |
||||
fi |
||||
fi |
||||
|
||||
dinfo "saving opalcore:$OPALCORE to $1/opalcore" |
||||
if ! cp $OPALCORE "$1/opalcore"; then |
||||
derror "saving opalcore failed" |
||||
return 1 |
||||
fi |
||||
|
||||
sync |
||||
dinfo "saving opalcore complete" |
||||
return 0 |
||||
} |
||||
|
||||
dump_to_rootfs() |
||||
{ |
||||
|
||||
if [ "$(systemctl status dracut-initqueue | sed -n "s/^\s*Active: \(\S*\)\s.*$/\1/p")" = "inactive" ]; then |
||||
dinfo "Trying to bring up initqueue for rootfs mount" |
||||
systemctl start dracut-initqueue |
||||
fi |
||||
|
||||
dinfo "Clean up dead systemd services" |
||||
systemctl cancel |
||||
dinfo "Waiting for rootfs mount, will timeout after 90 seconds" |
||||
systemctl start --no-block sysroot.mount |
||||
|
||||
_loop=0 |
||||
while [ $_loop -lt 90 ] && ! is_mounted /sysroot; do |
||||
sleep 1 |
||||
_loop=$((_loop + 1)) |
||||
done |
||||
|
||||
if ! is_mounted /sysroot; then |
||||
derror "Failed to mount rootfs" |
||||
return |
||||
fi |
||||
|
||||
ddebug "NEWROOT=$NEWROOT" |
||||
dump_fs $NEWROOT |
||||
} |
||||
|
||||
kdump_emergency_shell() |
||||
{ |
||||
ddebug "Switching to kdump emergency shell..." |
||||
|
||||
[ -f /etc/profile ] && . /etc/profile |
||||
export PS1='kdump:${PWD}# ' |
||||
|
||||
. /lib/dracut-lib.sh |
||||
if [ -f /dracut-state.sh ]; then |
||||
. /dracut-state.sh 2> /dev/null |
||||
fi |
||||
|
||||
source_conf /etc/conf.d |
||||
|
||||
type plymouth > /dev/null 2>&1 && plymouth quit |
||||
|
||||
source_hook "emergency" |
||||
while read -r _tty rest; do |
||||
( |
||||
echo |
||||
echo |
||||
echo 'Entering kdump emergency mode.' |
||||
echo 'Type "journalctl" to view system logs.' |
||||
echo 'Type "rdsosreport" to generate a sosreport, you can then' |
||||
echo 'save it elsewhere and attach it to a bug report.' |
||||
echo |
||||
echo |
||||
) > "/dev/$_tty" |
||||
done < /proc/consoles |
||||
sh -i -l |
||||
/bin/rm -f -- /.console_lock |
||||
} |
||||
|
||||
do_failure_action() |
||||
{ |
||||
dinfo "Executing failure action $FAILURE_ACTION" |
||||
eval $FAILURE_ACTION |
||||
} |
||||
|
||||
do_final_action() |
||||
{ |
||||
dinfo "Executing final action $FINAL_ACTION" |
||||
eval $FINAL_ACTION |
||||
} |
||||
|
||||
do_dump() |
||||
{ |
||||
eval $DUMP_INSTRUCTION |
||||
_ret=$? |
||||
|
||||
if [ $_ret -ne 0 ]; then |
||||
derror "saving vmcore failed" |
||||
fi |
||||
|
||||
return $_ret |
||||
} |
||||
|
||||
do_kdump_pre() |
||||
{ |
||||
if [ -n "$KDUMP_PRE" ]; then |
||||
"$KDUMP_PRE" |
||||
_ret=$? |
||||
if [ $_ret -ne 0 ]; then |
||||
derror "$KDUMP_PRE exited with $_ret status" |
||||
return $_ret |
||||
fi |
||||
fi |
||||
|
||||
# if any script fails, it just raises warning and continues |
||||
if [ -d /etc/kdump/pre.d ]; then |
||||
for file in /etc/kdump/pre.d/*; do |
||||
"$file" |
||||
_ret=$? |
||||
if [ $_ret -ne 0 ]; then |
||||
derror "$file exited with $_ret status" |
||||
fi |
||||
done |
||||
fi |
||||
return 0 |
||||
} |
||||
|
||||
do_kdump_post() |
||||
{ |
||||
if [ -d /etc/kdump/post.d ]; then |
||||
for file in /etc/kdump/post.d/*; do |
||||
"$file" "$1" |
||||
_ret=$? |
||||
if [ $_ret -ne 0 ]; then |
||||
derror "$file exited with $_ret status" |
||||
fi |
||||
done |
||||
fi |
||||
|
||||
if [ -n "$KDUMP_POST" ]; then |
||||
"$KDUMP_POST" "$1" |
||||
_ret=$? |
||||
if [ $_ret -ne 0 ]; then |
||||
derror "$KDUMP_POST exited with $_ret status" |
||||
fi |
||||
fi |
||||
} |
||||
|
||||
# $1: block target, eg. /dev/sda |
||||
dump_raw() |
||||
{ |
||||
[ -b "$1" ] || return 1 |
||||
|
||||
dinfo "saving to raw disk $1" |
||||
|
||||
if ! echo "$CORE_COLLECTOR" | grep -q makedumpfile; then |
||||
_src_size=$(stat --format %s /proc/vmcore) |
||||
_src_size_mb=$((_src_size / 1048576)) |
||||
/kdumpscripts/monitor_dd_progress $_src_size_mb & |
||||
fi |
||||
|
||||
dinfo "saving vmcore" |
||||
$CORE_COLLECTOR /proc/vmcore | dd of="$1" bs=$DD_BLKSIZE >> /tmp/dd_progress_file 2>&1 || return 1 |
||||
sync |
||||
|
||||
dinfo "saving vmcore complete" |
||||
return 0 |
||||
} |
||||
|
||||
# $1: ssh key file |
||||
# $2: ssh address in <user>@<host> format |
||||
dump_ssh() |
||||
{ |
||||
_ret=0 |
||||
_ssh_opt="-i $1 -o BatchMode=yes -o StrictHostKeyChecking=yes" |
||||
_ssh_dir="$KDUMP_PATH/$HOST_IP-$DATEDIR" |
||||
if is_ipv6_address "$2"; then |
||||
_scp_address=${2%@*}@"[${2#*@}]" |
||||
else |
||||
_scp_address=$2 |
||||
fi |
||||
|
||||
dinfo "saving to $2:$_ssh_dir" |
||||
|
||||
cat /var/lib/random-seed > /dev/urandom |
||||
ssh -q $_ssh_opt "$2" mkdir -p "$_ssh_dir" || return 1 |
||||
|
||||
save_vmcore_dmesg_ssh "$DMESG_COLLECTOR" "$_ssh_dir" "$_ssh_opt" "$2" |
||||
dinfo "saving vmcore" |
||||
|
||||
save_opalcore_ssh "$_ssh_dir" "$_ssh_opt" "$2" "$_scp_address" |
||||
|
||||
if [ "${CORE_COLLECTOR%%[[:blank:]]*}" = "scp" ]; then |
||||
scp -q $_ssh_opt /proc/vmcore "$_scp_address:$_ssh_dir/vmcore-incomplete" |
||||
_ret=$? |
||||
_vmcore="vmcore" |
||||
else |
||||
$CORE_COLLECTOR /proc/vmcore | ssh $_ssh_opt "$2" "umask 0077 && dd bs=512 of='$_ssh_dir/vmcore-incomplete'" |
||||
_ret=$? |
||||
_vmcore="vmcore.flat" |
||||
fi |
||||
|
||||
if [ $_ret -eq 0 ]; then |
||||
ssh $_ssh_opt "$2" "mv '$_ssh_dir/vmcore-incomplete' '$_ssh_dir/$_vmcore'" |
||||
_ret=$? |
||||
if [ $_ret -ne 0 ]; then |
||||
derror "moving vmcore failed, exitcode:$_ret" |
||||
else |
||||
dinfo "saving vmcore complete" |
||||
fi |
||||
else |
||||
derror "saving vmcore failed, exitcode:$_ret" |
||||
fi |
||||
|
||||
dinfo "saving the $KDUMP_LOG_FILE to $2:$_ssh_dir/" |
||||
save_log |
||||
if ! scp -q $_ssh_opt $KDUMP_LOG_FILE "$_scp_address:$_ssh_dir/"; then |
||||
derror "saving log file failed, _exitcode:$_ret" |
||||
fi |
||||
|
||||
return $_ret |
||||
} |
||||
|
||||
# $1: dump path |
||||
# $2: ssh opts |
||||
# $3: ssh address in <user>@<host> format |
||||
# $4: scp address, similar with ssh address but IPv6 addresses are quoted |
||||
save_opalcore_ssh() |
||||
{ |
||||
if [ ! -f $OPALCORE ]; then |
||||
# Check if we are on an old kernel that uses a different path |
||||
if [ -f /sys/firmware/opal/core ]; then |
||||
OPALCORE="/sys/firmware/opal/core" |
||||
else |
||||
return 0 |
||||
fi |
||||
fi |
||||
|
||||
dinfo "saving opalcore:$OPALCORE to $3:$1" |
||||
|
||||
if ! scp $2 $OPALCORE "$4:$1/opalcore-incomplete"; then |
||||
derror "saving opalcore failed" |
||||
return 1 |
||||
fi |
||||
|
||||
ssh $2 "$3" mv "$1/opalcore-incomplete" "$1/opalcore" |
||||
dinfo "saving opalcore complete" |
||||
return 0 |
||||
} |
||||
|
||||
# $1: dmesg collector |
||||
# $2: dump path |
||||
# $3: ssh opts |
||||
# $4: ssh address in <user>@<host> format |
||||
save_vmcore_dmesg_ssh() |
||||
{ |
||||
dinfo "saving vmcore-dmesg.txt to $4:$2" |
||||
if $1 /proc/vmcore | ssh $3 "$4" "umask 0077 && dd of='$2/vmcore-dmesg-incomplete.txt'"; then |
||||
ssh -q $3 "$4" mv "$2/vmcore-dmesg-incomplete.txt" "$2/vmcore-dmesg.txt" |
||||
dinfo "saving vmcore-dmesg.txt complete" |
||||
else |
||||
derror "saving vmcore-dmesg.txt failed" |
||||
fi |
||||
} |
||||
|
||||
get_host_ip() |
||||
{ |
||||
if is_nfs_dump_target || is_ssh_dump_target; then |
||||
kdumpnic=$(getarg kdumpnic=) |
||||
if [ -z "$kdumpnic" ]; then |
||||
derror "failed to get kdumpnic!" |
||||
return 1 |
||||
fi |
||||
if ! kdumphost=$(ip addr show dev "$kdumpnic" | grep '[ ]*inet'); then |
||||
derror "wrong kdumpnic: $kdumpnic" |
||||
return 1 |
||||
fi |
||||
kdumphost=$(echo "$kdumphost" | head -n 1 | awk '{print $2}') |
||||
kdumphost="${kdumphost%%/*}" |
||||
if [ -z "$kdumphost" ]; then |
||||
derror "wrong kdumpnic: $kdumpnic" |
||||
return 1 |
||||
fi |
||||
HOST_IP=$kdumphost |
||||
fi |
||||
return 0 |
||||
} |
||||
|
||||
read_kdump_confs() |
||||
{ |
||||
if [ ! -f "$KDUMP_CONFIG_FILE" ]; then |
||||
derror "$KDUMP_CONFIG_FILE not found" |
||||
return |
||||
fi |
||||
|
||||
get_kdump_confs |
||||
|
||||
# rescan for add code for dump target |
||||
while read -r config_opt config_val; do |
||||
# remove inline comments after the end of a directive. |
||||
case "$config_opt" in |
||||
dracut_args) |
||||
config_val=$(get_dracut_args_target "$config_val") |
||||
if [ -n "$config_val" ]; then |
||||
config_val=$(get_mntpoint_from_target "$config_val") |
||||
DUMP_INSTRUCTION="dump_fs $config_val" |
||||
fi |
||||
;; |
||||
ext[234] | xfs | btrfs | minix | nfs) |
||||
config_val=$(get_mntpoint_from_target "$config_val") |
||||
DUMP_INSTRUCTION="dump_fs $config_val" |
||||
;; |
||||
raw) |
||||
DUMP_INSTRUCTION="dump_raw $config_val" |
||||
;; |
||||
ssh) |
||||
DUMP_INSTRUCTION="dump_ssh $SSH_KEY_LOCATION $config_val" |
||||
;; |
||||
esac |
||||
done < "$KDUMP_CONF_PARSED" |
||||
} |
||||
|
||||
fence_kdump_notify() |
||||
{ |
||||
if [ -n "$FENCE_KDUMP_NODES" ]; then |
||||
# shellcheck disable=SC2086 |
||||
$FENCE_KDUMP_SEND $FENCE_KDUMP_ARGS $FENCE_KDUMP_NODES & |
||||
fi |
||||
} |
||||
|
||||
if [ "$1" = "--error-handler" ]; then |
||||
get_kdump_confs |
||||
do_failure_action |
||||
do_final_action |
||||
|
||||
exit $? |
||||
fi |
||||
|
||||
# continue here only if we have to save dump. |
||||
if [ -f /etc/fadump.initramfs ] && [ ! -f /proc/device-tree/rtas/ibm,kernel-dump ] && [ ! -f /proc/device-tree/ibm,opal/dump/mpipl-boot ]; then |
||||
exit 0 |
||||
fi |
||||
|
||||
read_kdump_confs |
||||
fence_kdump_notify |
||||
|
||||
if ! get_host_ip; then |
||||
derror "get_host_ip exited with non-zero status!" |
||||
exit 1 |
||||
fi |
||||
|
||||
if [ -z "$DUMP_INSTRUCTION" ]; then |
||||
DUMP_INSTRUCTION="dump_fs $NEWROOT" |
||||
fi |
||||
|
||||
if ! do_kdump_pre; then |
||||
derror "kdump_pre script exited with non-zero status!" |
||||
do_final_action |
||||
# During systemd service to reboot the machine, stop this shell script running |
||||
exit 1 |
||||
fi |
||||
make_trace_mem "kdump saving vmcore" '1:shortmem' '2+:mem' '3+:slab' |
||||
do_dump |
||||
DUMP_RETVAL=$? |
||||
|
||||
if ! do_kdump_post $DUMP_RETVAL; then |
||||
derror "kdump_post script exited with non-zero status!" |
||||
fi |
||||
|
||||
if [ $DUMP_RETVAL -ne 0 ]; then |
||||
exit 1 |
||||
fi |
||||
|
||||
do_final_action |
||||
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,28 @@
@@ -0,0 +1,28 @@
|
||||
#!/bin/sh |
||||
|
||||
SRC_FILE_MB=$1 |
||||
|
||||
while true |
||||
do |
||||
DD_PID=`pidof dd` |
||||
if [ -n "$DD_PID" ]; then |
||||
break |
||||
fi |
||||
done |
||||
|
||||
while true |
||||
do |
||||
sleep 5 |
||||
if [ ! -d /proc/$DD_PID ]; then |
||||
break |
||||
fi |
||||
|
||||
kill -s USR1 $DD_PID |
||||
CURRENT_SIZE=`tail -n 1 /tmp/dd_progress_file | sed "s/[^0-9].*//g"` |
||||
[ -n "$CURRENT_SIZE" ] && { |
||||
CURRENT_MB=$(($CURRENT_SIZE / 1048576)) |
||||
echo -e "Copied $CURRENT_MB MB / $SRC_FILE_MB MB\r" |
||||
} |
||||
done |
||||
|
||||
rm -f /tmp/dd_progress_file |
||||
@ -0,0 +1,95 @@
@@ -0,0 +1,95 @@
|
||||
Early Kdump HOWTO |
||||
|
||||
Introduction |
||||
------------ |
||||
|
||||
Early kdump is a mechanism to make kdump operational earlier than normal kdump |
||||
service. The kdump service starts early enough for general crash cases, but |
||||
there are some cases where it has no chance to make kdump operational in boot |
||||
sequence, such as detecting devices and starting early services. If you hit |
||||
such a case, early kdump may allow you to get more information of it. |
||||
|
||||
Early kdump is implemented as a dracut module. It adds a kernel (vmlinuz) and |
||||
initramfs for kdump to your system's initramfs in order to load them as early |
||||
as possible. After that, if you provide "rd.earlykdump" in kernel command line, |
||||
then in the initramfs, early kdump will load those files like the normal kdump |
||||
service. This is disabled by default. |
||||
|
||||
For the normal kdump service, it can check whether the early kdump has loaded |
||||
the crash kernel and initramfs. It has no conflict with the early kdump. |
||||
|
||||
How to configure early kdump |
||||
---------------------------- |
||||
|
||||
We assume if you're reading this document, you should already have kexec-tools |
||||
installed. |
||||
|
||||
You can rebuild the initramfs with earlykdump support with below steps: |
||||
|
||||
1. start kdump service to make sure kdump initramfs is created. |
||||
|
||||
# systemctl start kdump |
||||
|
||||
NOTE: If a crash occurs during boot process, early kdump captures a vmcore |
||||
and reboot the system by default, so the system might go into crash loop. |
||||
You can avoid such a crash loop by adding the following settings, which |
||||
power off the system after dump capturing, to kdump.conf in advance: |
||||
|
||||
final_action poweroff |
||||
failure_action poweroff |
||||
|
||||
For the failure_action, you can choose anything other than "reboot". |
||||
|
||||
2. rebuild system initramfs with earlykdump support. |
||||
|
||||
# dracut --force --add earlykdump |
||||
|
||||
NOTE: Recommend to backup the original system initramfs before performing |
||||
this step to put it back if something happens during boot-up. |
||||
|
||||
3. add rd.earlykdump in grub kernel command line. |
||||
|
||||
After making said changes, reboot your system to take effect. Of course, if you |
||||
want to disable early kdump, you can simply remove "rd.earlykdump" from kernel |
||||
boot parameters in grub, and reboot system like above. |
||||
|
||||
Once the boot is completed, you can check the status of the early kdump support |
||||
on the command prompt: |
||||
|
||||
# journalctl -b | grep early-kdump |
||||
|
||||
Then, you will see some useful logs, for example: |
||||
|
||||
- if early kdump is successful. |
||||
|
||||
Mar 09 09:57:56 localhost dracut-cmdline[190]: early-kdump is enabled. |
||||
Mar 09 09:57:56 localhost dracut-cmdline[190]: kexec: loaded early-kdump kernel |
||||
|
||||
- if early kdump is disabled. |
||||
|
||||
Mar 09 10:02:47 localhost dracut-cmdline[189]: early-kdump is disabled. |
||||
|
||||
Notes |
||||
----- |
||||
|
||||
- The size of early kdump initramfs will be large because it includes vmlinuz |
||||
and kdump initramfs. |
||||
|
||||
- Early kdump inherits the settings of normal kdump, so any changes that |
||||
caused normal kdump rebuilding also require rebuilding the system initramfs |
||||
to make sure that the changes take effect for early kdump. Therefore, after |
||||
the rebuilding of kdump initramfs is completed, provide a prompt message to |
||||
tell the fact. |
||||
|
||||
- If you install an updated kernel and reboot the system with it, the early |
||||
kdump will be disabled by default. To enable it with the new kernel, you |
||||
need to take the above steps again. |
||||
|
||||
Limitation |
||||
---------- |
||||
|
||||
- At present, early kdump doesn't support fadump. |
||||
|
||||
- Early kdump loads a crash kernel and initramfs at the beginning of the |
||||
process in system's initramfs, so a crash at earlier than that (e.g. in |
||||
kernel initialization) cannot be captured even with the early kdump. |
||||
@ -0,0 +1,355 @@
@@ -0,0 +1,355 @@
|
||||
Firmware assisted dump (fadump) HOWTO |
||||
|
||||
Introduction |
||||
|
||||
Firmware assisted dump is a new feature in the 3.4 mainline kernel supported |
||||
only on powerpc architecture. The goal of firmware-assisted dump is to enable |
||||
the dump of a crashed system, and to do so from a fully-reset system, and to |
||||
minimize the total elapsed time until the system is back in production use. A |
||||
complete documentation on implementation can be found at |
||||
Documentation/powerpc/firmware-assisted-dump.txt in upstream linux kernel tree |
||||
from 3.4 version and above. |
||||
|
||||
Please note that the firmware-assisted dump feature is only available on Power6 |
||||
and above systems with recent firmware versions. |
||||
|
||||
Overview |
||||
|
||||
Fadump |
||||
|
||||
Fadump is a robust kernel crash dumping mechanism to get reliable kernel crash |
||||
dump with assistance from firmware. This approach does not use kexec, instead |
||||
firmware assists in booting the kdump kernel while preserving memory contents. |
||||
Unlike kdump, the system is fully reset, and loaded with a fresh copy of the |
||||
kernel. In particular, PCI and I/O devices are reinitialized and are in a |
||||
clean, consistent state. This second kernel, often called a capture kernel, |
||||
boots with very little memory and captures the dump image. |
||||
|
||||
The first kernel registers the sections of memory with the Power firmware for |
||||
dump preservation during OS initialization. These registered sections of memory |
||||
are reserved by the first kernel during early boot. When a system crashes, the |
||||
Power firmware fully resets the system, preserves all the system memory |
||||
contents, save the low memory (boot memory of size larger of 5% of system |
||||
RAM or 256MB) of RAM to the previous registered region. It will also save |
||||
system registers, and hardware PTE's. |
||||
|
||||
Fadump is supported only on ppc64 platform. The standard kernel and capture |
||||
kernel are one and the same on ppc64. |
||||
|
||||
If you're reading this document, you should already have kexec-tools |
||||
installed. If not, you install it via the following command: |
||||
|
||||
# yum install kexec-tools |
||||
|
||||
Fadump Operational Flow: |
||||
|
||||
Like kdump, fadump also exports the ELF formatted kernel crash dump through |
||||
/proc/vmcore. Hence existing kdump infrastructure can be used to capture fadump |
||||
vmcore. The idea is to keep the functionality transparent to end user. From |
||||
user perspective there is no change in the way kdump init script works. |
||||
|
||||
However, unlike kdump, fadump does not pre-load kdump kernel and initrd into |
||||
reserved memory, instead it always uses default OS initrd during second boot |
||||
after crash. Hence, for fadump, we rebuild the new kdump initrd and replace it |
||||
with default initrd. Before replacing existing default initrd we take a backup |
||||
of original default initrd for user's reference. The dracut package has been |
||||
enhanced to rebuild the default initrd with vmcore capture steps. The initrd |
||||
image is rebuilt as per the configuration in /etc/kdump.conf file. |
||||
|
||||
The control flow of fadump works as follows: |
||||
01. System panics. |
||||
02. At the crash, kernel informs power firmware that kernel has crashed. |
||||
03. Firmware takes the control and reboots the entire system preserving |
||||
only the memory (resets all other devices). |
||||
04. The reboot follows the normal booting process (non-kexec). |
||||
05. The boot loader loads the default kernel and initrd from /boot |
||||
06. The default initrd loads and runs /init |
||||
07. dracut-kdump.sh script present in fadump aware default initrd checks if |
||||
'/proc/device-tree/rtas/ibm,kernel-dump' file exists before executing |
||||
steps to capture vmcore. |
||||
(This check will help to bypass the vmcore capture steps during normal boot |
||||
process.) |
||||
09. Captures dump according to /etc/kdump.conf |
||||
10. Is dump capture successful (yes goto 12, no goto 11) |
||||
11. Perform the failure action specified in /etc/kdump.conf |
||||
(The default failure action is reboot, if unspecified) |
||||
12. Perform the final action specified in /etc/kdump.conf |
||||
(The default final action is reboot, if unspecified) |
||||
|
||||
|
||||
How to configure fadump: |
||||
|
||||
Again, we assume if you're reading this document, you should already have |
||||
kexec-tools installed. If not, you install it via the following command: |
||||
|
||||
# yum install kexec-tools |
||||
|
||||
Make the kernel to be configured with FADump as the default boot entry, if |
||||
it isn't already: |
||||
|
||||
# grubby --set-default=/boot/vmlinuz-<kver> |
||||
|
||||
Boot into the kernel to be configured for FADump. To be able to do much of |
||||
anything interesting in the way of debug analysis, you'll also need to install |
||||
the kernel-debuginfo package, of the same arch as your running kernel, and the |
||||
crash utility: |
||||
|
||||
# yum --enablerepo=\*debuginfo install kernel-debuginfo.$(uname -m) crash |
||||
|
||||
Next up, we need to modify some boot parameters to enable firmware assisted |
||||
dump. With the help of grubby, it's very easy to append "fadump=on" to the end |
||||
of your kernel boot parameters. To reserve the appropriate amount of memory |
||||
for boot memory preservation, pass 'crashkernel=X' kernel cmdline parameter. |
||||
For the recommended value of X, see 'FADump Memory Requirements' section. |
||||
|
||||
# grubby --args="fadump=on crashkernel=6G" --update-kernel=/boot/vmlinuz-`uname -r` |
||||
|
||||
By default, FADump reserved memory will be initialized as CMA area to make the |
||||
memory available through CMA allocator on the production kernel. We can opt out |
||||
of this, making reserved memory unavailable to production kernel, by booting the |
||||
linux kernel with 'fadump=nocma' instead of 'fadump=on'. |
||||
|
||||
The term 'boot memory' means size of the low memory chunk that is required for |
||||
a kernel to boot successfully when booted with restricted memory. By default, |
||||
the boot memory size will be the larger of 5% of system RAM or 256MB. |
||||
Alternatively, user can also specify boot memory size through boot parameter |
||||
'fadump_reserve_mem=' which will override the default calculated size. Use this |
||||
option if default boot memory size is not sufficient for second kernel to boot |
||||
successfully. |
||||
|
||||
After making said changes, reboot your system, so that the specified memory is |
||||
reserved and left untouched by the normal system. Take note that the output of |
||||
'free -m' will show X MB less memory than without this parameter, which is |
||||
expected. If you see OOM (Out Of Memory) error messages while loading capture |
||||
kernel, then you should bump up the memory reservation size. |
||||
|
||||
Now that you've got that reserved memory region set up, you want to turn on |
||||
the kdump init script: |
||||
|
||||
# systemctl enable kdump.service |
||||
|
||||
Then, start up kdump as well: |
||||
|
||||
# systemctl start kdump.service |
||||
|
||||
This should turn on the firmware assisted functionality in kernel by |
||||
echo'ing 1 to /sys/kernel/fadump_registered, leaving the system ready |
||||
to capture a vmcore upon crashing. For journaling filesystems like XFS an |
||||
additional step is required to ensure bootloader does not pick the |
||||
older initrd (without vmcore capture scripts): |
||||
|
||||
* If /boot is a separate partition, run the below commands as the root user, |
||||
or as a user with CAP_SYS_ADMIN rights: |
||||
|
||||
# fsfreeze -f |
||||
# fsfreeze -u |
||||
|
||||
* If /boot is not a separate partition, reboot the system. |
||||
|
||||
After reboot check if the kdump service is up and running with: |
||||
|
||||
# systemctl status kdump.service |
||||
|
||||
To test out whether FADump is configured properly, you can force-crash your |
||||
system by echo'ing a 'c' into /proc/sysrq-trigger: |
||||
|
||||
# echo c > /proc/sysrq-trigger |
||||
|
||||
You should see some panic output, followed by the system reset and booting into |
||||
fresh copy of kernel. When default initrd loads and runs /init, vmcore should |
||||
be copied out to disk (by default, in /var/crash/<YYYY.MM.DD-HH:MM:SS>/vmcore), |
||||
then the system rebooted back into your normal kernel. |
||||
|
||||
Once back to your normal kernel, you can use the previously installed crash |
||||
kernel in conjunction with the previously installed kernel-debuginfo to |
||||
perform postmortem analysis: |
||||
|
||||
# crash /usr/lib/debug/lib/modules/2.6.17-1.2621.el5/vmlinux |
||||
/var/crash/2006-08-23-15:34/vmcore |
||||
|
||||
crash> bt |
||||
|
||||
and so on... |
||||
|
||||
Saving vmcore-dmesg.txt |
||||
----------------------- |
||||
Kernel log bufferes are one of the most important information available |
||||
in vmcore. Now before saving vmcore, kernel log bufferes are extracted |
||||
from /proc/vmcore and saved into a file vmcore-dmesg.txt. After |
||||
vmcore-dmesg.txt, vmcore is saved. Destination disk and directory for |
||||
vmcore-dmesg.txt is same as vmcore. Note that kernel log buffers will |
||||
not be available if dump target is raw device. |
||||
|
||||
FADump Memory Requirements: |
||||
|
||||
System Memory Recommended memory |
||||
--------------------- ---------------------- |
||||
4 GB - 16 GB : 768 MB |
||||
16 GB - 64 GB : 1024 MB |
||||
64 GB - 128 GB : 2 GB |
||||
128 GB - 1 TB : 4 GB |
||||
1 TB - 2 TB : 6 GB |
||||
2 TB - 4 TB : 12 GB |
||||
4 TB - 8 TB : 20 GB |
||||
8 TB - 16 TB : 36 GB |
||||
16 TB - 32 TB : 64 GB |
||||
32 TB - 64 TB : 128 GB |
||||
64 TB & above : 180 GB |
||||
|
||||
Things to remember: |
||||
|
||||
1) The memory required to boot capture Kernel is a moving target that depends |
||||
on many factors like hardware attached to the system, kernel and modules in |
||||
use, packages installed and services enabled, there is no one-size-fits-all. |
||||
But the above recommendations are based on system memory. So, the above |
||||
recommendations for FADump come with a few assumptions, based on available |
||||
system memory, about the resources the system could have. So, please take |
||||
the recommendations with a pinch of salt and remember to try capturing dump |
||||
a few times to confirm that the system is configured successfully with dump |
||||
capturing support. |
||||
|
||||
2) Though the memory requirements for FADump seem high, this memory is not |
||||
completely set aside but made available for userspace applications to use, |
||||
through the CMA allocator. |
||||
|
||||
3) As the same initrd is used for booting production kernel as well as capture |
||||
kernel and with dump being captured in a restricted memory environment, few |
||||
optimizations (like not inclding network dracut module, disabling multipath |
||||
and such) are applied while building the initrd. In case, the production |
||||
environment needs these optimizations to be avoided, dracut_args option in |
||||
/etc/kdump.conf file could be leveraged. For example, if a user wishes for |
||||
network module to be included in the initrd, adding the below entry in |
||||
/etc/kdump.conf file and restarting kdump service would take care of it. |
||||
|
||||
dracut_args --add "network" |
||||
|
||||
4) If FADump is configured to capture vmcore to a remote dump target using SSH |
||||
or NFS protocol, the corresponding network interface '<interface-name>' is |
||||
renamed to 'kdump-<interface-name>', if it is generic (like *eth# or net#). |
||||
It happens because vmcore capture scripts in the initial RAM disk (initrd) |
||||
add the 'kdump-' prefix to the network interface name to secure persistent |
||||
naming. And as capture kernel and production kernel use the same initrd in |
||||
case of FADump, the interface name is changed for the production kernel too. |
||||
This is likely to impact network configuration setup for production kernel. |
||||
So, it is recommended to use a non-generic name for a network interface, |
||||
before setting up FADump to capture vmcore to a remote dump target based on |
||||
that network interface, to avoid running into network configuration issues. |
||||
|
||||
Dump Triggering methods: |
||||
|
||||
This section talks about the various ways, other than a Kernel Panic, in which |
||||
fadump can be triggered. The following methods assume that fadump is configured |
||||
on your system, with the scripts enabled as described in the section above. |
||||
|
||||
1) AltSysRq C |
||||
|
||||
FAdump can be triggered with the combination of the 'Alt','SysRq' and 'C' |
||||
keyboard keys. Please refer to the following link for more details: |
||||
|
||||
https://fedoraproject.org/wiki/QA/Sysrq |
||||
|
||||
In addition, on PowerPC boxes, fadump can also be triggered via Hardware |
||||
Management Console(HMC) using 'Ctrl', 'O' and 'C' keyboard keys. |
||||
|
||||
2) Kernel OOPs |
||||
|
||||
If we want to generate a dump everytime the Kernel OOPses, we can achieve this |
||||
by setting the 'Panic On OOPs' option as follows: |
||||
|
||||
# echo 1 > /proc/sys/kernel/panic_on_oops |
||||
|
||||
3) PowerPC specific methods: |
||||
|
||||
On IBM PowerPC machines, issuing a soft reset invokes the XMON debugger(if |
||||
XMON is configured). To configure XMON one needs to compile the kernel with |
||||
the CONFIG_XMON and CONFIG_XMON_DEFAULT options, or by compiling with |
||||
CONFIG_XMON and booting the kernel with xmon=on option. |
||||
|
||||
Following are the ways to remotely issue a soft reset on PowerPC boxes, which |
||||
would drop you to XMON. Pressing a 'X' (capital alphabet X) followed by an |
||||
'Enter' here will trigger the dump. |
||||
|
||||
3.1) HMC |
||||
|
||||
Hardware Management Console(HMC) available on Power4 and Power5 machines allow |
||||
partitions to be reset remotely. This is specially useful in hang situations |
||||
where the system is not accepting any keyboard inputs. |
||||
|
||||
Once you have HMC configured, the following steps will enable you to trigger |
||||
fadump via a soft reset: |
||||
|
||||
On Power4 |
||||
Using GUI |
||||
|
||||
* In the right pane, right click on the partition you wish to dump. |
||||
* Select "Operating System->Reset". |
||||
* Select "Soft Reset". |
||||
* Select "Yes". |
||||
|
||||
Using HMC Commandline |
||||
|
||||
# reset_partition -m <machine> -p <partition> -t soft |
||||
|
||||
On Power5 |
||||
Using GUI |
||||
|
||||
* In the right pane, right click on the partition you wish to dump. |
||||
* Select "Restart Partition". |
||||
* Select "Dump". |
||||
* Select "OK". |
||||
|
||||
Using HMC Commandline |
||||
|
||||
# chsysstate -m <managed system name> -n <lpar name> -o dumprestart -r lpar |
||||
|
||||
3.2) Blade Management Console for Blade Center |
||||
|
||||
To initiate a dump operation, go to Power/Restart option under "Blade Tasks" in |
||||
the Blade Management Console. Select the corresponding blade for which you want |
||||
to initate the dump and then click "Restart blade with NMI". This issues a |
||||
system reset and invokes xmon debugger. |
||||
|
||||
|
||||
Advanced Setups & Failure action: |
||||
|
||||
Kdump and fadump exhibit similar behavior in terms of setup & failure action. |
||||
For fadump advanced setup related information see section "Advanced Setups" in |
||||
"kexec-kdump-howto.txt" document. Refer to "Failure action" section in "kexec- |
||||
kdump-howto.txt" document for fadump failure action related information. |
||||
|
||||
Compression and filtering |
||||
|
||||
Refer "Compression and filtering" section in "kexec-kdump-howto.txt" document. |
||||
Compression and filtering are same for kdump & fadump. |
||||
|
||||
|
||||
Notes on rootfs mount: |
||||
Dracut is designed to mount rootfs by default. If rootfs mounting fails it |
||||
will refuse to go on. So fadump leaves rootfs mounting to dracut currently. |
||||
We make the assumtion that proper root= cmdline is being passed to dracut |
||||
initramfs for the time being. If you need modify "KDUMP_COMMANDLINE=" in |
||||
/etc/sysconfig/kdump, you will need to make sure that appropriate root= |
||||
options are copied from /proc/cmdline. In general it is best to append |
||||
command line options using "KDUMP_COMMANDLINE_APPEND=" instead of replacing |
||||
the original command line completely. |
||||
|
||||
How to disable FADump: |
||||
|
||||
Remove "fadump=on"/"fadump=nocma" from kernel cmdline parameters OR replace |
||||
it with "fadump=off" kernel cmdline parameter: |
||||
|
||||
# grubby --update-kernel=/boot/vmlinuz-`uname -r` --remove-args="fadump=on" |
||||
or |
||||
# grubby --update-kernel=/boot/vmlinuz-`uname -r` --remove-args="fadump=nocma" |
||||
OR |
||||
# grubby --update-kernel=/boot/vmlinuz-`uname -r` --args="fadump=off" |
||||
|
||||
Remove "crashkernel=" from kernel cmdline parameters: |
||||
|
||||
# grubby --update-kernel=/boot/vmlinuz-`uname -r` --remove-args="crashkernel" |
||||
|
||||
If KDump is to be used as the dump capturing mechanism, reset the crashkernel parameter: |
||||
|
||||
# kdumpctl reset-crashkernel `uname -r` |
||||
|
||||
Reboot the system for the settings to take effect. |
||||
@ -0,0 +1,23 @@
@@ -0,0 +1,23 @@
|
||||
#!/bin/sh |
||||
|
||||
# More details about systemd generator: |
||||
# http://www.freedesktop.org/wiki/Software/systemd/Generators/ |
||||
|
||||
. /usr/lib/kdump/kdump-lib.sh |
||||
. /usr/lib/kdump/kdump-logger.sh |
||||
|
||||
# If invokded with no arguments for testing purpose, output to /tmp to |
||||
# avoid overriding the existing. |
||||
dest_dir="/tmp" |
||||
|
||||
if [ -n "$1" ]; then |
||||
dest_dir=$1 |
||||
fi |
||||
|
||||
systemd_dir=/usr/lib/systemd/system |
||||
kdump_wants=$dest_dir/kdump.service.wants |
||||
|
||||
if is_ssh_dump_target; then |
||||
mkdir -p $kdump_wants |
||||
ln -sf $systemd_dir/network-online.target $kdump_wants/ |
||||
fi |
||||
@ -0,0 +1,91 @@
@@ -0,0 +1,91 @@
|
||||
Kdump-in-cluster-environment HOWTO |
||||
|
||||
Introduction |
||||
|
||||
Kdump is a kexec based crash dumping mechansim for Linux. This docuement |
||||
illustrate how to configure kdump in cluster environment to allow the kdump |
||||
crash recovery service complete without being preempted by traditional power |
||||
fencing methods. |
||||
|
||||
Overview |
||||
|
||||
Kexec/Kdump |
||||
|
||||
Details about Kexec/Kdump are available in Kexec-Kdump-howto file and will not |
||||
be described here. |
||||
|
||||
fence_kdump |
||||
|
||||
fence_kdump is an I/O fencing agent to be used with the kdump crash recovery |
||||
service. When the fence_kdump agent is invoked, it will listen for a message |
||||
from the failed node that acknowledges that the failed node is executing the |
||||
kdump crash kernel. Note that fence_kdump is not a replacement for traditional |
||||
fencing methods. The fence_kdump agent can only detect that a node has entered |
||||
the kdump crash recovery service. This allows the kdump crash recovery service |
||||
complete without being preempted by traditional power fencing methods. |
||||
|
||||
fence_kdump_send |
||||
|
||||
fence_kdump_send is a utility used to send messages that acknowledge that the |
||||
node itself has entered the kdump crash recovery service. The fence_kdump_send |
||||
utility is typically run in the kdump kernel after a cluster node has |
||||
encountered a kernel panic. Once the cluster node has entered the kdump crash |
||||
recovery service, fence_kdump_send will periodically send messages to all |
||||
cluster nodes. When the fence_kdump agent receives a valid message from the |
||||
failed nodes, fencing is complete. |
||||
|
||||
How to configure Pacemaker cluster environment: |
||||
|
||||
If we want to use kdump in Pacemaker cluster environment, fence-agents-kdump |
||||
should be installed in every nodes in the cluster. You can achieve this via |
||||
the following command: |
||||
|
||||
# yum install -y fence-agents-kdump |
||||
|
||||
Next is to add kdump_fence to the cluster. Assuming that the cluster consists |
||||
of three nodes, they are node1, node2 and node3, and use Pacemaker to perform |
||||
resource management and pcs as cli configuration tool. |
||||
|
||||
With pcs it is easy to add a stonith resource to the cluster. For example, add |
||||
a stonith resource named mykdumpfence with fence type of fence_kdump via the |
||||
following commands: |
||||
|
||||
# pcs stonith create mykdumpfence fence_kdump \ |
||||
pcmk_host_check=static-list pcmk_host_list="node1 node2 node3" |
||||
# pcs stonith update mykdumpfence pcmk_monitor_action=metadata --force |
||||
# pcs stonith update mykdumpfence pcmk_status_action=metadata --force |
||||
# pcs stonith update mykdumpfence pcmk_reboot_action=off --force |
||||
|
||||
Then enable stonith |
||||
# pcs property set stonith-enabled=true |
||||
|
||||
How to configure kdump: |
||||
|
||||
Actually there are two ways how to configure fence_kdump support: |
||||
|
||||
1) Pacemaker based clusters |
||||
If you have successfully configured fence_kdump in Pacemaker, there is |
||||
no need to add some special configuration in kdump. So please refer to |
||||
Kexec-Kdump-howto file for more information. |
||||
|
||||
2) Generic clusters |
||||
For other types of clusters there are two configuration options in |
||||
kdump.conf which enables fence_kdump support: |
||||
|
||||
fence_kdump_nodes <node(s)> |
||||
Contains list of cluster node(s) separated by space to send |
||||
fence_kdump notification to (this option is mandatory to enable |
||||
fence_kdump) |
||||
|
||||
fence_kdump_args <arg(s)> |
||||
Command line arguments for fence_kdump_send (it can contain |
||||
all valid arguments except hosts to send notification to) |
||||
|
||||
These options will most probably be configured by your cluster software, |
||||
so please refer to your cluster documentation how to enable fence_kdump |
||||
support. |
||||
|
||||
Please be aware that these two ways cannot be combined and 2) has precedence |
||||
over 1). It means that if fence_kdump is configured using fence_kdump_nodes |
||||
and fence_kdump_args options in kdump.conf, Pacemaker configuration is not |
||||
used even if it exists. |
||||
@ -0,0 +1,132 @@
@@ -0,0 +1,132 @@
|
||||
#!/bin/sh |
||||
# |
||||
# The code in this file will be used in initramfs environment, bash may |
||||
# not be the default shell. Any code added must be POSIX compliant. |
||||
|
||||
DEFAULT_PATH="/var/crash/" |
||||
KDUMP_CONFIG_FILE="/etc/kdump.conf" |
||||
FENCE_KDUMP_CONFIG_FILE="/etc/sysconfig/fence_kdump" |
||||
FENCE_KDUMP_SEND="/usr/libexec/fence_kdump_send" |
||||
|
||||
# Read kdump config in well formated style |
||||
kdump_read_conf() |
||||
{ |
||||
# Following steps are applied in order: strip trailing comment, strip trailing space, |
||||
# strip heading space, match non-empty line, remove duplicated spaces between conf name and value |
||||
[ -f "$KDUMP_CONFIG_FILE" ] && sed -n -e "s/#.*//;s/\s*$//;s/^\s*//;s/\(\S\+\)\s*\(.*\)/\1 \2/p" $KDUMP_CONFIG_FILE |
||||
} |
||||
|
||||
# Retrieves config value defined in kdump.conf |
||||
# $1: config name, sed regexp compatible |
||||
kdump_get_conf_val() |
||||
{ |
||||
# For lines matching "^\s*$1\s+", remove matched part (config name including space), |
||||
# remove tailing comment, space, then store in hold space. Print out the hold buffer on last line. |
||||
[ -f "$KDUMP_CONFIG_FILE" ] && |
||||
sed -n -e "/^\s*\($1\)\s\+/{s/^\s*\($1\)\s\+//;s/#.*//;s/\s*$//;h};\${x;p}" $KDUMP_CONFIG_FILE |
||||
} |
||||
|
||||
is_mounted() |
||||
{ |
||||
findmnt -k -n "$1" > /dev/null 2>&1 |
||||
} |
||||
|
||||
# $1: info type |
||||
# $2: mount source type |
||||
# $3: mount source |
||||
# $4: extra args |
||||
get_mount_info() |
||||
{ |
||||
__kdump_mnt=$(findmnt -k -n -r -o "$1" "--$2" "$3" $4) |
||||
|
||||
[ -z "$__kdump_mnt" ] && [ -e "/etc/fstab" ] && __kdump_mnt=$(findmnt -s -n -r -o "$1" "--$2" "$3" $4) |
||||
|
||||
echo "$__kdump_mnt" |
||||
} |
||||
|
||||
is_ipv6_address() |
||||
{ |
||||
echo "$1" | grep -q ":" |
||||
} |
||||
|
||||
is_fs_type_nfs() |
||||
{ |
||||
[ "$1" = "nfs" ] || [ "$1" = "nfs4" ] |
||||
} |
||||
|
||||
# If $1 contains dracut_args "--mount", return <filesystem type> |
||||
get_dracut_args_fstype() |
||||
{ |
||||
echo $1 | grep "\-\-mount" | sed "s/.*--mount .\(.*\)/\1/" | cut -d' ' -f3 |
||||
} |
||||
|
||||
# If $1 contains dracut_args "--mount", return <device> |
||||
get_dracut_args_target() |
||||
{ |
||||
echo $1 | grep "\-\-mount" | sed "s/.*--mount .\(.*\)/\1/" | cut -d' ' -f1 |
||||
} |
||||
|
||||
get_save_path() |
||||
{ |
||||
__kdump_path=$(kdump_get_conf_val path) |
||||
[ -z "$__kdump_path" ] && __kdump_path=$DEFAULT_PATH |
||||
|
||||
# strip the duplicated "/" |
||||
echo "$__kdump_path" | tr -s / |
||||
} |
||||
|
||||
get_root_fs_device() |
||||
{ |
||||
findmnt -k -f -n -o SOURCE / |
||||
} |
||||
|
||||
# Return the current underlying device of a path, ignore bind mounts |
||||
get_target_from_path() |
||||
{ |
||||
__kdump_target=$(df "$1" 2> /dev/null | tail -1 | awk '{print $1}') |
||||
[ "$__kdump_target" = "/dev/root" ] && [ ! -e /dev/root ] && __kdump_target=$(get_root_fs_device) |
||||
echo "$__kdump_target" |
||||
} |
||||
|
||||
get_fs_type_from_target() |
||||
{ |
||||
get_mount_info FSTYPE source "$1" -f |
||||
} |
||||
|
||||
get_mntpoint_from_target() |
||||
{ |
||||
# --source is applied to ensure non-bind mount is returned |
||||
get_mount_info TARGET source "$1" -f |
||||
} |
||||
|
||||
is_ssh_dump_target() |
||||
{ |
||||
kdump_get_conf_val ssh | grep -q @ |
||||
} |
||||
|
||||
is_raw_dump_target() |
||||
{ |
||||
[ -n "$(kdump_get_conf_val raw)" ] |
||||
} |
||||
|
||||
is_nfs_dump_target() |
||||
{ |
||||
if [ -n "$(kdump_get_conf_val nfs)" ]; then |
||||
return 0 |
||||
fi |
||||
|
||||
if is_fs_type_nfs "$(get_dracut_args_fstype "$(kdump_get_conf_val dracut_args)")"; then |
||||
return 0 |
||||
fi |
||||
|
||||
if is_fs_type_nfs "$(get_fs_type_from_target "$(get_target_from_path "$(get_save_path)")")"; then |
||||
return 0 |
||||
fi |
||||
|
||||
return 1 |
||||
} |
||||
|
||||
is_fs_dump_target() |
||||
{ |
||||
[ -n "$(kdump_get_conf_val "ext[234]\|xfs\|btrfs\|minix")" ] |
||||
} |
||||
@ -0,0 +1,989 @@
@@ -0,0 +1,989 @@
|
||||
#!/bin/bash |
||||
# |
||||
# Kdump common variables and functions |
||||
# |
||||
|
||||
. /usr/lib/kdump/kdump-lib-initramfs.sh |
||||
|
||||
FADUMP_ENABLED_SYS_NODE="/sys/kernel/fadump_enabled" |
||||
|
||||
is_fadump_capable() |
||||
{ |
||||
# Check if firmware-assisted dump is enabled |
||||
# if no, fallback to kdump check |
||||
if [[ -f $FADUMP_ENABLED_SYS_NODE ]]; then |
||||
rc=$(< $FADUMP_ENABLED_SYS_NODE) |
||||
[[ $rc -eq 1 ]] && return 0 |
||||
fi |
||||
return 1 |
||||
} |
||||
|
||||
is_squash_available() |
||||
{ |
||||
for kmodule in squashfs overlay loop; do |
||||
if [[ -z $KDUMP_KERNELVER ]]; then |
||||
modprobe --dry-run $kmodule &> /dev/null || return 1 |
||||
else |
||||
modprobe -S "$KDUMP_KERNELVER" --dry-run $kmodule &> /dev/null || return 1 |
||||
fi |
||||
done |
||||
} |
||||
|
||||
is_zstd_command_available() |
||||
{ |
||||
[[ -x "$(command -v zstd)" ]] |
||||
} |
||||
|
||||
perror_exit() |
||||
{ |
||||
derror "$@" |
||||
exit 1 |
||||
} |
||||
|
||||
# Check if fence kdump is configured in Pacemaker cluster |
||||
is_pcs_fence_kdump() |
||||
{ |
||||
# no pcs or fence_kdump_send executables installed? |
||||
type -P pcs > /dev/null || return 1 |
||||
[[ -x $FENCE_KDUMP_SEND ]] || return 1 |
||||
|
||||
# fence kdump not configured? |
||||
(pcs cluster cib | grep 'type="fence_kdump"') &> /dev/null || return 1 |
||||
} |
||||
|
||||
# Check if fence_kdump is configured using kdump options |
||||
is_generic_fence_kdump() |
||||
{ |
||||
[[ -x $FENCE_KDUMP_SEND ]] || return 1 |
||||
|
||||
[[ $(kdump_get_conf_val fence_kdump_nodes) ]] |
||||
} |
||||
|
||||
to_dev_name() |
||||
{ |
||||
local dev="${1//\"/}" |
||||
|
||||
case "$dev" in |
||||
UUID=*) |
||||
blkid -U "${dev#UUID=}" |
||||
;; |
||||
LABEL=*) |
||||
blkid -L "${dev#LABEL=}" |
||||
;; |
||||
*) |
||||
echo "$dev" |
||||
;; |
||||
esac |
||||
} |
||||
|
||||
is_user_configured_dump_target() |
||||
{ |
||||
[[ $(kdump_get_conf_val "ext[234]\|xfs\|btrfs\|minix\|raw\|nfs\|ssh") ]] || is_mount_in_dracut_args |
||||
} |
||||
|
||||
get_user_configured_dump_disk() |
||||
{ |
||||
local _target |
||||
|
||||
_target=$(kdump_get_conf_val "ext[234]\|xfs\|btrfs\|minix\|raw") |
||||
[[ -n $_target ]] && echo "$_target" && return |
||||
|
||||
_target=$(get_dracut_args_target "$(kdump_get_conf_val "dracut_args")") |
||||
[[ -b $_target ]] && echo "$_target" |
||||
} |
||||
|
||||
get_block_dump_target() |
||||
{ |
||||
local _target _path |
||||
|
||||
if is_ssh_dump_target || is_nfs_dump_target; then |
||||
return |
||||
fi |
||||
|
||||
_target=$(get_user_configured_dump_disk) |
||||
[[ -n $_target ]] && to_dev_name "$_target" && return |
||||
|
||||
# Get block device name from local save path |
||||
_path=$(get_save_path) |
||||
_target=$(get_target_from_path "$_path") |
||||
[[ -b $_target ]] && to_dev_name "$_target" |
||||
} |
||||
|
||||
is_dump_to_rootfs() |
||||
{ |
||||
[[ $(kdump_get_conf_val 'failure_action\|default') == dump_to_rootfs ]] |
||||
} |
||||
|
||||
get_failure_action_target() |
||||
{ |
||||
local _target |
||||
|
||||
if is_dump_to_rootfs; then |
||||
# Get rootfs device name |
||||
_target=$(get_root_fs_device) |
||||
[[ -b $_target ]] && to_dev_name "$_target" && return |
||||
# Then, must be nfs root |
||||
echo "nfs" |
||||
fi |
||||
} |
||||
|
||||
# Get kdump targets(including root in case of dump_to_rootfs). |
||||
get_kdump_targets() |
||||
{ |
||||
local _target _root |
||||
local kdump_targets |
||||
|
||||
_target=$(get_block_dump_target) |
||||
if [[ -n $_target ]]; then |
||||
kdump_targets=$_target |
||||
elif is_ssh_dump_target; then |
||||
kdump_targets="ssh" |
||||
else |
||||
kdump_targets="nfs" |
||||
fi |
||||
|
||||
# Add the root device if dump_to_rootfs is specified. |
||||
_root=$(get_failure_action_target) |
||||
if [[ -n $_root ]] && [[ $kdump_targets != "$_root" ]]; then |
||||
kdump_targets="$kdump_targets $_root" |
||||
fi |
||||
|
||||
echo "$kdump_targets" |
||||
} |
||||
|
||||
# Return the bind mount source path, return the path itself if it's not bind mounted |
||||
# Eg. if /path/to/src is bind mounted to /mnt/bind, then: |
||||
# /mnt/bind -> /path/to/src, /mnt/bind/dump -> /path/to/src/dump |
||||
# |
||||
# findmnt uses the option "-v, --nofsroot" to exclusive the [/dir] |
||||
# in the SOURCE column for bind-mounts, then if $_src equals to |
||||
# $_src_nofsroot, the mountpoint is not bind mounted directory. |
||||
# |
||||
# Below is just an example for mount info |
||||
# /dev/mapper/atomicos-root[/ostree/deploy/rhel-atomic-host/var], if the |
||||
# directory is bind mounted. The former part represents the device path, rest |
||||
# part is the bind mounted directory which quotes by bracket "[]". |
||||
get_bind_mount_source() |
||||
{ |
||||
local _mnt _path _src _opt _fstype |
||||
local _fsroot _src_nofsroot |
||||
|
||||
_mnt=$(df "$1" | tail -1 | awk '{print $NF}') |
||||
_path=${1#$_mnt} |
||||
|
||||
_src=$(get_mount_info SOURCE target "$_mnt" -f) |
||||
_opt=$(get_mount_info OPTIONS target "$_mnt" -f) |
||||
_fstype=$(get_mount_info FSTYPE target "$_mnt" -f) |
||||
|
||||
# bind mount in fstab |
||||
if [[ -d $_src ]] && [[ $_fstype == none ]] && (echo "$_opt" | grep -q "\bbind\b"); then |
||||
echo "$_src$_path" && return |
||||
fi |
||||
|
||||
# direct mount |
||||
_src_nofsroot=$(get_mount_info SOURCE target "$_mnt" -v -f) |
||||
if [[ $_src_nofsroot == "$_src" ]]; then |
||||
echo "$_mnt$_path" && return |
||||
fi |
||||
|
||||
_fsroot=${_src#${_src_nofsroot}[} |
||||
_fsroot=${_fsroot%]} |
||||
_mnt=$(get_mount_info TARGET source "$_src_nofsroot" -f) |
||||
|
||||
# for btrfs, _fsroot will also contain the subvol value as well, strip it |
||||
if [[ $_fstype == btrfs ]]; then |
||||
local _subvol |
||||
_subvol=${_opt#*subvol=} |
||||
_subvol=${_subvol%,*} |
||||
_fsroot=${_fsroot#$_subvol} |
||||
fi |
||||
echo "$_mnt$_fsroot$_path" |
||||
} |
||||
|
||||
get_mntopt_from_target() |
||||
{ |
||||
get_mount_info OPTIONS source "$1" -f |
||||
} |
||||
|
||||
# Get the path where the target will be mounted in kdump kernel |
||||
# $1: kdump target device |
||||
get_kdump_mntpoint_from_target() |
||||
{ |
||||
local _mntpoint |
||||
|
||||
_mntpoint=$(get_mntpoint_from_target "$1") |
||||
# mount under /sysroot if dump to root disk or mount under |
||||
# mount under /kdumproot if dump target is not mounted in first kernel |
||||
# mount under /kdumproot/$_mntpoint in other cases in 2nd kernel. |
||||
# systemd will be in charge to umount it. |
||||
if [[ -z $_mntpoint ]]; then |
||||
_mntpoint="/kdumproot" |
||||
else |
||||
if [[ $_mntpoint == "/" ]]; then |
||||
_mntpoint="/sysroot" |
||||
else |
||||
_mntpoint="/kdumproot/$_mntpoint" |
||||
fi |
||||
fi |
||||
|
||||
# strip duplicated "/" |
||||
echo $_mntpoint | tr -s "/" |
||||
} |
||||
|
||||
kdump_get_persistent_dev() |
||||
{ |
||||
local dev="${1//\"/}" |
||||
|
||||
case "$dev" in |
||||
UUID=*) |
||||
dev=$(blkid -U "${dev#UUID=}") |
||||
;; |
||||
LABEL=*) |
||||
dev=$(blkid -L "${dev#LABEL=}") |
||||
;; |
||||
esac |
||||
echo $(get_persistent_dev "$dev") |
||||
} |
||||
|
||||
is_atomic() |
||||
{ |
||||
grep -q "ostree" /proc/cmdline |
||||
} |
||||
|
||||
# get ip address or hostname from nfs/ssh config value |
||||
get_remote_host() |
||||
{ |
||||
local _config_val=$1 |
||||
|
||||
# ipv6 address in kdump.conf is around with "[]", |
||||
# factor out the ipv6 address |
||||
_config_val=${_config_val#*@} |
||||
_config_val=${_config_val%:/*} |
||||
_config_val=${_config_val#[} |
||||
_config_val=${_config_val%]} |
||||
echo "$_config_val" |
||||
} |
||||
|
||||
is_hostname() |
||||
{ |
||||
local _hostname |
||||
|
||||
_hostname=$(echo "$1" | grep ":") |
||||
if [[ -n $_hostname ]]; then |
||||
return 1 |
||||
fi |
||||
echo "$1" | grep -q "[a-zA-Z]" |
||||
} |
||||
|
||||
# Copied from "/etc/sysconfig/network-scripts/network-functions" |
||||
get_hwaddr() |
||||
{ |
||||
if [[ -f "/sys/class/net/$1/address" ]]; then |
||||
awk '{ print toupper($0) }' < "/sys/class/net/$1/address" |
||||
elif [[ -d "/sys/class/net/$1" ]]; then |
||||
LC_ALL="" LANG="" ip -o link show "$1" 2> /dev/null | |
||||
awk '{ print toupper(gensub(/.*link\/[^ ]* ([[:alnum:]:]*).*/, |
||||
"\\1", 1)); }' |
||||
fi |
||||
} |
||||
|
||||
# Get value by a field using "nmcli -g" |
||||
# Usage: get_nmcli_value_by_field <field> <nmcli command> |
||||
# |
||||
# "nmcli --get-values" allows us to retrive value(s) by field, for example, |
||||
# nmcli --get-values <field> connection show /org/freedesktop/NetworkManager/ActiveConnection/1 |
||||
# returns the following value for the corresponding field respectively, |
||||
# Field Value |
||||
# IP4.DNS "10.19.42.41 | 10.11.5.19 | 10.5.30.160" |
||||
# 802-3-ethernet.s390-subchannels "" |
||||
# bond.options "mode=balance-rr" |
||||
get_nmcli_value_by_field() |
||||
{ |
||||
LANG=C nmcli --get-values "$@" |
||||
} |
||||
|
||||
# Get nmcli field value of an connection apath (a D-Bus active connection path) |
||||
# Usage: get_nmcli_field_by_apath <field> <apath> |
||||
get_nmcli_field_by_conpath() |
||||
{ |
||||
local _field=$1 _apath=$2 |
||||
|
||||
get_nmcli_value_by_field "$_field" connection show "$_apath" |
||||
} |
||||
|
||||
# Get nmcli connection apath (a D-Bus active connection path ) by ifname |
||||
# |
||||
# apath is used for nmcli connection operations, e.g. |
||||
# $ nmcli connection show $apath |
||||
get_nmcli_connection_apath_by_ifname() |
||||
{ |
||||
local _ifname=$1 |
||||
|
||||
get_nmcli_value_by_field "GENERAL.CON-PATH" device show "$_ifname" |
||||
} |
||||
|
||||
get_ifcfg_by_device() |
||||
{ |
||||
grep -E -i -l "^[[:space:]]*DEVICE=\"*${1}\"*[[:space:]]*$" \ |
||||
/etc/sysconfig/network-scripts/ifcfg-* 2> /dev/null | head -1 |
||||
} |
||||
|
||||
get_ifcfg_by_hwaddr() |
||||
{ |
||||
grep -E -i -l "^[[:space:]]*HWADDR=\"*${1}\"*[[:space:]]*$" \ |
||||
/etc/sysconfig/network-scripts/ifcfg-* 2> /dev/null | head -1 |
||||
} |
||||
|
||||
get_ifcfg_by_uuid() |
||||
{ |
||||
grep -E -i -l "^[[:space:]]*UUID=\"*${1}\"*[[:space:]]*$" \ |
||||
/etc/sysconfig/network-scripts/ifcfg-* 2> /dev/null | head -1 |
||||
} |
||||
|
||||
get_ifcfg_by_name() |
||||
{ |
||||
grep -E -i -l "^[[:space:]]*NAME=\"*${1}\"*[[:space:]]*$" \ |
||||
/etc/sysconfig/network-scripts/ifcfg-* 2> /dev/null | head -1 |
||||
} |
||||
|
||||
is_nm_running() |
||||
{ |
||||
[[ "$(LANG=C nmcli -t --fields running general status 2> /dev/null)" == "running" ]] |
||||
} |
||||
|
||||
is_nm_handling() |
||||
{ |
||||
LANG=C nmcli -t --fields device,state dev status 2> /dev/null | |
||||
grep -q "^\(${1}:connected\)\|\(${1}:connecting.*\)$" |
||||
} |
||||
|
||||
# $1: netdev name |
||||
get_ifcfg_nmcli() |
||||
{ |
||||
local nm_uuid nm_name |
||||
local ifcfg_file |
||||
|
||||
# Get the active nmcli config name of $1 |
||||
if is_nm_running && is_nm_handling "${1}"; then |
||||
# The configuration "uuid" and "name" generated by nm is wrote to |
||||
# the ifcfg file as "UUID=<nm_uuid>" and "NAME=<nm_name>". |
||||
nm_uuid=$(LANG=C nmcli -t --fields uuid,device c show --active 2> /dev/null | |
||||
grep "${1}" | head -1 | cut -d':' -f1) |
||||
nm_name=$(LANG=C nmcli -t --fields name,device c show --active 2> /dev/null | |
||||
grep "${1}" | head -1 | cut -d':' -f1) |
||||
ifcfg_file=$(get_ifcfg_by_uuid "${nm_uuid}") |
||||
[[ -z ${ifcfg_file} ]] && ifcfg_file=$(get_ifcfg_by_name "${nm_name}") |
||||
fi |
||||
|
||||
echo -n "${ifcfg_file}" |
||||
} |
||||
|
||||
# $1: netdev name |
||||
get_ifcfg_legacy() |
||||
{ |
||||
local ifcfg_file hwaddr |
||||
|
||||
ifcfg_file="/etc/sysconfig/network-scripts/ifcfg-${1}" |
||||
[[ -f ${ifcfg_file} ]] && echo -n "${ifcfg_file}" && return |
||||
|
||||
ifcfg_file=$(get_ifcfg_by_name "${1}") |
||||
[[ -f ${ifcfg_file} ]] && echo -n "${ifcfg_file}" && return |
||||
|
||||
hwaddr=$(get_hwaddr "${1}") |
||||
if [[ -n $hwaddr ]]; then |
||||
ifcfg_file=$(get_ifcfg_by_hwaddr "${hwaddr}") |
||||
[[ -f ${ifcfg_file} ]] && echo -n "${ifcfg_file}" && return |
||||
fi |
||||
|
||||
ifcfg_file=$(get_ifcfg_by_device "${1}") |
||||
|
||||
echo -n "${ifcfg_file}" |
||||
} |
||||
|
||||
# $1: netdev name |
||||
# Return the ifcfg file whole name(including the path) of $1 if any. |
||||
get_ifcfg_filename() |
||||
{ |
||||
local ifcfg_file |
||||
|
||||
ifcfg_file=$(get_ifcfg_nmcli "${1}") |
||||
if [[ -z ${ifcfg_file} ]]; then |
||||
ifcfg_file=$(get_ifcfg_legacy "${1}") |
||||
fi |
||||
|
||||
echo -n "${ifcfg_file}" |
||||
} |
||||
|
||||
# returns 0 when omission of a module is desired in dracut_args |
||||
# returns 1 otherwise |
||||
is_dracut_mod_omitted() |
||||
{ |
||||
local dracut_args dracut_mod=$1 |
||||
|
||||
set -- $(kdump_get_conf_val dracut_args) |
||||
while [ $# -gt 0 ]; do |
||||
case $1 in |
||||
-o | --omit) |
||||
[[ " ${2//[^[:alnum:]]/ } " == *" $dracut_mod "* ]] && return 0 |
||||
;; |
||||
esac |
||||
shift |
||||
done |
||||
|
||||
return 1 |
||||
} |
||||
|
||||
is_wdt_active() |
||||
{ |
||||
local active |
||||
|
||||
[[ -d /sys/class/watchdog ]] || return 1 |
||||
for dir in /sys/class/watchdog/*; do |
||||
[[ -f "$dir/state" ]] || continue |
||||
active=$(< "$dir/state") |
||||
[[ $active == "active" ]] && return 0 |
||||
done |
||||
return 1 |
||||
} |
||||
|
||||
have_compression_in_dracut_args() |
||||
{ |
||||
[[ "$(kdump_get_conf_val dracut_args)" =~ \ |
||||
(^|[[:space:]])--(gzip|bzip2|lzma|xz|lzo|lz4|zstd|no-compress|compress)([[:space:]]|$) ]] |
||||
} |
||||
|
||||
# If "dracut_args" contains "--mount" information, use it |
||||
# directly without any check(users are expected to ensure |
||||
# its correctness). |
||||
is_mount_in_dracut_args() |
||||
{ |
||||
[[ " $(kdump_get_conf_val dracut_args)" =~ .*[[:space:]]--mount[=[:space:]].* ]] |
||||
} |
||||
|
||||
check_crash_mem_reserved() |
||||
{ |
||||
local mem_reserved |
||||
|
||||
mem_reserved=$(< /sys/kernel/kexec_crash_size) |
||||
if [[ $mem_reserved -eq 0 ]]; then |
||||
derror "No memory reserved for crash kernel" |
||||
return 1 |
||||
fi |
||||
|
||||
return 0 |
||||
} |
||||
|
||||
check_kdump_feasibility() |
||||
{ |
||||
if [[ ! -e /sys/kernel/kexec_crash_loaded ]]; then |
||||
derror "Kdump is not supported on this kernel" |
||||
return 1 |
||||
fi |
||||
check_crash_mem_reserved |
||||
return $? |
||||
} |
||||
|
||||
check_current_kdump_status() |
||||
{ |
||||
if [[ ! -f /sys/kernel/kexec_crash_loaded ]]; then |
||||
derror "Perhaps CONFIG_CRASH_DUMP is not enabled in kernel" |
||||
return 1 |
||||
fi |
||||
|
||||
rc=$(< /sys/kernel/kexec_crash_loaded) |
||||
if [[ $rc == 1 ]]; then |
||||
return 0 |
||||
else |
||||
return 1 |
||||
fi |
||||
} |
||||
|
||||
# remove_cmdline_param <kernel cmdline> <param1> [<param2>] ... [<paramN>] |
||||
# Remove a list of kernel parameters from a given kernel cmdline and print the result. |
||||
# For each "arg" in the removing params list, "arg" and "arg=xxx" will be removed if exists. |
||||
remove_cmdline_param() |
||||
{ |
||||
local cmdline=$1 |
||||
shift |
||||
|
||||
for arg in "$@"; do |
||||
cmdline=$(echo "$cmdline" | |
||||
sed -e "s/\b$arg=[^ ]*//g" \ |
||||
-e "s/^$arg\b//g" \ |
||||
-e "s/[[:space:]]$arg\b//g" \ |
||||
-e "s/\s\+/ /g") |
||||
done |
||||
echo "$cmdline" |
||||
} |
||||
|
||||
# |
||||
# This function returns the "apicid" of the boot |
||||
# cpu (cpu 0) if present. |
||||
# |
||||
get_bootcpu_apicid() |
||||
{ |
||||
awk ' \ |
||||
BEGIN { CPU = "-1"; } \ |
||||
$1=="processor" && $2==":" { CPU = $NF; } \ |
||||
CPU=="0" && /^apicid/ { print $NF; } \ |
||||
' \ |
||||
/proc/cpuinfo |
||||
} |
||||
|
||||
# |
||||
# append_cmdline <kernel cmdline> <parameter name> <parameter value> |
||||
# This function appends argument "$2=$3" to string ($1) if not already present. |
||||
# |
||||
append_cmdline() |
||||
{ |
||||
local cmdline=$1 |
||||
local newstr=${cmdline/$2/""} |
||||
|
||||
# unchanged str implies argument wasn't there |
||||
if [[ $cmdline == "$newstr" ]]; then |
||||
cmdline="${cmdline} ${2}=${3}" |
||||
fi |
||||
|
||||
echo "$cmdline" |
||||
} |
||||
|
||||
# This function check iomem and determines if we have more than |
||||
# 4GB of ram available. Returns 1 if we do, 0 if we dont |
||||
need_64bit_headers() |
||||
{ |
||||
return "$(tail -n 1 /proc/iomem | awk '{ split ($1, r, "-"); |
||||
print (strtonum("0x" r[2]) > strtonum("0xffffffff")); }')" |
||||
} |
||||
|
||||
# Check if secure boot is being enforced. |
||||
# |
||||
# Per Peter Jones, we need check efivar SecureBoot-$(the UUID) and |
||||
# SetupMode-$(the UUID), they are both 5 bytes binary data. The first four |
||||
# bytes are the attributes associated with the variable and can safely be |
||||
# ignored, the last bytes are one-byte true-or-false variables. If SecureBoot |
||||
# is 1 and SetupMode is 0, then secure boot is being enforced. |
||||
# |
||||
# Assume efivars is mounted at /sys/firmware/efi/efivars. |
||||
is_secure_boot_enforced() |
||||
{ |
||||
local secure_boot_file setup_mode_file |
||||
local secure_boot_byte setup_mode_byte |
||||
|
||||
# On powerpc, secure boot is enforced if: |
||||
# host secure boot: /ibm,secure-boot/os-secureboot-enforcing DT property exists |
||||
# guest secure boot: /ibm,secure-boot >= 2 |
||||
if [[ -f /proc/device-tree/ibm,secureboot/os-secureboot-enforcing ]]; then |
||||
return 0 |
||||
fi |
||||
if [[ -f /proc/device-tree/ibm,secure-boot ]] && |
||||
[[ $(lsprop /proc/device-tree/ibm,secure-boot | tail -1) -ge 2 ]]; then |
||||
return 0 |
||||
fi |
||||
|
||||
# Detect secure boot on x86 and arm64 |
||||
secure_boot_file=$(find /sys/firmware/efi/efivars -name "SecureBoot-*" 2> /dev/null) |
||||
setup_mode_file=$(find /sys/firmware/efi/efivars -name "SetupMode-*" 2> /dev/null) |
||||
|
||||
if [[ -f $secure_boot_file ]] && [[ -f $setup_mode_file ]]; then |
||||
secure_boot_byte=$(hexdump -v -e '/1 "%d\ "' "$secure_boot_file" | cut -d' ' -f 5) |
||||
setup_mode_byte=$(hexdump -v -e '/1 "%d\ "' "$setup_mode_file" | cut -d' ' -f 5) |
||||
|
||||
if [[ $secure_boot_byte == "1" ]] && [[ $setup_mode_byte == "0" ]]; then |
||||
return 0 |
||||
fi |
||||
fi |
||||
|
||||
# Detect secure boot on s390x |
||||
if [[ -e "/sys/firmware/ipl/secure" && "$(< /sys/firmware/ipl/secure)" == "1" ]]; then |
||||
return 0 |
||||
fi |
||||
|
||||
return 1 |
||||
} |
||||
|
||||
# |
||||
# prepare_kexec_args <kexec args> |
||||
# This function prepares kexec argument. |
||||
# |
||||
prepare_kexec_args() |
||||
{ |
||||
local kexec_args=$1 |
||||
local found_elf_args |
||||
|
||||
ARCH=$(uname -m) |
||||
if [[ $ARCH == "i686" ]] || [[ $ARCH == "i386" ]]; then |
||||
need_64bit_headers |
||||
if [[ $? == 1 ]]; then |
||||
found_elf_args=$(echo "$kexec_args" | grep elf32-core-headers) |
||||
if [[ -n $found_elf_args ]]; then |
||||
dwarn "Warning: elf32-core-headers overrides correct elf64 setting" |
||||
else |
||||
kexec_args="$kexec_args --elf64-core-headers" |
||||
fi |
||||
else |
||||
found_elf_args=$(echo "$kexec_args" | grep elf64-core-headers) |
||||
if [[ -z $found_elf_args ]]; then |
||||
kexec_args="$kexec_args --elf32-core-headers" |
||||
fi |
||||
fi |
||||
fi |
||||
echo "$kexec_args" |
||||
} |
||||
|
||||
# |
||||
# Detect initrd and kernel location, results are stored in global enviromental variables: |
||||
# KDUMP_BOOTDIR, KDUMP_KERNELVER, KDUMP_KERNEL, DEFAULT_INITRD, and KDUMP_INITRD |
||||
# |
||||
# Expectes KDUMP_BOOTDIR, KDUMP_IMG, KDUMP_IMG_EXT, KDUMP_KERNELVER to be loaded from config already |
||||
# and will prefer already set values so user can specify custom kernel/initramfs location |
||||
# |
||||
prepare_kdump_bootinfo() |
||||
{ |
||||
local boot_img boot_imglist boot_dirlist boot_initrdlist |
||||
local machine_id |
||||
|
||||
if [[ -z $KDUMP_KERNELVER ]]; then |
||||
KDUMP_KERNELVER="$(uname -r)" |
||||
fi |
||||
|
||||
read -r machine_id < /etc/machine-id |
||||
boot_dirlist=${KDUMP_BOOTDIR:-"/boot /boot/efi /efi /"} |
||||
boot_imglist="$KDUMP_IMG-$KDUMP_KERNELVER$KDUMP_IMG_EXT $machine_id/$KDUMP_KERNELVER/$KDUMP_IMG" |
||||
|
||||
# Use BOOT_IMAGE as reference if possible, strip the GRUB root device prefix in (hd0,gpt1) format |
||||
boot_img="$(sed "s/^BOOT_IMAGE=\((\S*)\)\?\(\S*\) .*/\2/" /proc/cmdline)" |
||||
if [[ -n $boot_img ]]; then |
||||
boot_imglist="$boot_img $boot_imglist" |
||||
fi |
||||
|
||||
for dir in $boot_dirlist; do |
||||
for img in $boot_imglist; do |
||||
if [[ -f "$dir/$img" ]]; then |
||||
KDUMP_KERNEL=$(echo "$dir/$img" | tr -s '/') |
||||
break 2 |
||||
fi |
||||
done |
||||
done |
||||
|
||||
if ! [[ -e $KDUMP_KERNEL ]]; then |
||||
derror "Failed to detect kdump kernel location" |
||||
return 1 |
||||
fi |
||||
|
||||
# Set KDUMP_BOOTDIR to where kernel image is stored |
||||
KDUMP_BOOTDIR=$(dirname "$KDUMP_KERNEL") |
||||
|
||||
# Default initrd should just stay aside of kernel image, try to find it in KDUMP_BOOTDIR |
||||
boot_initrdlist="initramfs-$KDUMP_KERNELVER.img initrd" |
||||
for initrd in $boot_initrdlist; do |
||||
if [[ -f "$KDUMP_BOOTDIR/$initrd" ]]; then |
||||
defaut_initrd_base="$initrd" |
||||
DEFAULT_INITRD="$KDUMP_BOOTDIR/$defaut_initrd_base" |
||||
break |
||||
fi |
||||
done |
||||
|
||||
# Create kdump initrd basename from default initrd basename |
||||
# initramfs-5.7.9-200.fc32.x86_64.img => initramfs-5.7.9-200.fc32.x86_64kdump.img |
||||
# initrd => initrdkdump |
||||
if [[ -z $defaut_initrd_base ]]; then |
||||
kdump_initrd_base=initramfs-${KDUMP_KERNELVER}kdump.img |
||||
elif [[ $defaut_initrd_base == *.* ]]; then |
||||
kdump_initrd_base=${defaut_initrd_base%.*}kdump.${DEFAULT_INITRD##*.} |
||||
else |
||||
kdump_initrd_base=${defaut_initrd_base}kdump |
||||
fi |
||||
|
||||
# Place kdump initrd in $(/var/lib/kdump) if $(KDUMP_BOOTDIR) not writable |
||||
if [[ ! -w $KDUMP_BOOTDIR ]]; then |
||||
var_target_initrd_dir="/var/lib/kdump" |
||||
mkdir -p "$var_target_initrd_dir" |
||||
KDUMP_INITRD="$var_target_initrd_dir/$kdump_initrd_base" |
||||
else |
||||
KDUMP_INITRD="$KDUMP_BOOTDIR/$kdump_initrd_base" |
||||
fi |
||||
} |
||||
|
||||
get_watchdog_drvs() |
||||
{ |
||||
local _wdtdrvs _drv _dir |
||||
|
||||
for _dir in /sys/class/watchdog/*; do |
||||
# device/modalias will return driver of this device |
||||
[[ -f "$_dir/device/modalias" ]] || continue |
||||
_drv=$(< "$_dir/device/modalias") |
||||
_drv=$(modprobe --set-version "$KDUMP_KERNELVER" -R "$_drv" 2> /dev/null) |
||||
for i in $_drv; do |
||||
if ! [[ " $_wdtdrvs " == *" $i "* ]]; then |
||||
_wdtdrvs="$_wdtdrvs $i" |
||||
fi |
||||
done |
||||
done |
||||
|
||||
echo "$_wdtdrvs" |
||||
} |
||||
|
||||
# |
||||
# prepare_cmdline <commandline> <commandline remove> <commandline append> |
||||
# This function performs a series of edits on the command line. |
||||
# Store the final result in global $KDUMP_COMMANDLINE. |
||||
prepare_cmdline() |
||||
{ |
||||
local cmdline id arg |
||||
|
||||
if [[ -z $1 ]]; then |
||||
cmdline=$(< /proc/cmdline) |
||||
else |
||||
cmdline="$1" |
||||
fi |
||||
|
||||
# These params should always be removed |
||||
cmdline=$(remove_cmdline_param "$cmdline" crashkernel panic_on_warn) |
||||
# These params can be removed configurably |
||||
while read -r arg; do |
||||
cmdline=$(remove_cmdline_param "$cmdline" "$arg") |
||||
done <<< "$(echo "$2" | xargs -n 1 echo)" |
||||
|
||||
# Always remove "root=X", as we now explicitly generate all kinds |
||||
# of dump target mount information including root fs. |
||||
# |
||||
# We do this before KDUMP_COMMANDLINE_APPEND, if one really cares |
||||
# about it(e.g. for debug purpose), then can pass "root=X" using |
||||
# KDUMP_COMMANDLINE_APPEND. |
||||
cmdline=$(remove_cmdline_param "$cmdline" root) |
||||
|
||||
# With the help of "--hostonly-cmdline", we can avoid some interitage. |
||||
cmdline=$(remove_cmdline_param "$cmdline" rd.lvm.lv rd.luks.uuid rd.dm.uuid rd.md.uuid fcoe) |
||||
|
||||
# Remove netroot, rd.iscsi.initiator and iscsi_initiator since |
||||
# we get duplicate entries for the same in case iscsi code adds |
||||
# it as well. |
||||
cmdline=$(remove_cmdline_param "$cmdline" netroot rd.iscsi.initiator iscsi_initiator) |
||||
|
||||
cmdline="${cmdline} $3" |
||||
|
||||
id=$(get_bootcpu_apicid) |
||||
if [[ -n ${id} ]]; then |
||||
cmdline=$(append_cmdline "$cmdline" disable_cpu_apicid "$id") |
||||
fi |
||||
|
||||
# If any watchdog is used, set it's pretimeout to 0. pretimeout let |
||||
# watchdog panic the kernel first, and reset the system after the |
||||
# panic. If the system is already in kdump, panic is not helpful |
||||
# and only increase the chance of watchdog failure. |
||||
for i in $(get_watchdog_drvs); do |
||||
cmdline+=" $i.pretimeout=0" |
||||
|
||||
if [[ $i == hpwdt ]]; then |
||||
# hpwdt have a special parameter kdumptimeout, is's only suppose |
||||
# to be set to non-zero in first kernel. In kdump, non-zero |
||||
# value could prevent the watchdog from resetting the system. |
||||
cmdline+=" $i.kdumptimeout=0" |
||||
fi |
||||
done |
||||
|
||||
echo "$cmdline" |
||||
} |
||||
|
||||
#get system memory size in the unit of GB |
||||
get_system_size() |
||||
{ |
||||
result=$(grep "System RAM" /proc/iomem | awk -F ":" '{ print $1 }' | tr "[:lower:]" "[:upper:]" | paste -sd+) |
||||
result="+$result" |
||||
# replace '-' with '+0x' and '+' with '-0x' |
||||
sum=$(echo "$result" | sed -e 's/-/K0x/g' -e 's/+/-0x/g' -e 's/K/+/g') |
||||
size=$(printf "%d\n" $((sum))) |
||||
size=$((size / 1024 / 1024 / 1024)) |
||||
|
||||
echo "$size" |
||||
} |
||||
|
||||
get_recommend_size() |
||||
{ |
||||
local mem_size=$1 |
||||
local _ck_cmdline=$2 |
||||
local OLDIFS="$IFS" |
||||
|
||||
start=${_ck_cmdline::1} |
||||
if [[ $mem_size -lt $start ]]; then |
||||
echo "0M" |
||||
return |
||||
fi |
||||
IFS=',' |
||||
for i in $_ck_cmdline; do |
||||
end=$(echo "$i" | awk -F "-" '{ print $2 }' | awk -F ":" '{ print $1 }') |
||||
recommend=$(echo "$i" | awk -F "-" '{ print $2 }' | awk -F ":" '{ print $2 }') |
||||
size=${end::-1} |
||||
unit=${end: -1} |
||||
if [[ $unit == 'T' ]]; then |
||||
size=$((size * 1024)) |
||||
fi |
||||
if [[ $mem_size -lt $size ]]; then |
||||
echo "$recommend" |
||||
IFS="$OLDIFS" |
||||
return |
||||
fi |
||||
done |
||||
IFS="$OLDIFS" |
||||
} |
||||
|
||||
# get default crashkernel |
||||
# $1 dump mode, if not specified, dump_mode will be judged by is_fadump_capable |
||||
kdump_get_arch_recommend_crashkernel() |
||||
{ |
||||
local _arch _ck_cmdline _dump_mode |
||||
|
||||
if [[ -z "$1" ]]; then |
||||
if is_fadump_capable; then |
||||
_dump_mode=fadump |
||||
else |
||||
_dump_mode=kdump |
||||
fi |
||||
else |
||||
_dump_mode=$1 |
||||
fi |
||||
|
||||
_arch=$(uname -m) |
||||
|
||||
if [[ $_arch == "x86_64" ]] || [[ $_arch == "s390x" ]]; then |
||||
_ck_cmdline="1G-4G:192M,4G-64G:256M,64G-:512M" |
||||
elif [[ $_arch == "aarch64" ]]; then |
||||
_ck_cmdline="2G-:448M" |
||||
elif [[ $_arch == "ppc64le" ]]; then |
||||
if [[ $_dump_mode == "fadump" ]]; then |
||||
_ck_cmdline="4G-16G:768M,16G-64G:1G,64G-128G:2G,128G-1T:4G,1T-2T:6G,2T-4T:12G,4T-8T:20G,8T-16T:36G,16T-32T:64G,32T-64T:128G,64T-:180G" |
||||
else |
||||
_ck_cmdline="2G-4G:384M,4G-16G:512M,16G-64G:1G,64G-128G:2G,128G-:4G" |
||||
fi |
||||
fi |
||||
|
||||
echo -n "$_ck_cmdline" |
||||
} |
||||
|
||||
# return recommended size based on current system RAM size |
||||
# $1: kernel version, if not set, will defaults to $(uname -r) |
||||
kdump_get_arch_recommend_size() |
||||
{ |
||||
local _ck_cmdline _sys_mem |
||||
|
||||
if ! [[ -r "/proc/iomem" ]]; then |
||||
echo "Error, can not access /proc/iomem." |
||||
return 1 |
||||
fi |
||||
_sys_mem=$(get_system_size) |
||||
_ck_cmdline=$(kdump_get_arch_recommend_crashkernel) |
||||
_ck_cmdline=${_ck_cmdline//-:/-102400T:} |
||||
get_recommend_size "$_sys_mem" "$_ck_cmdline" |
||||
} |
||||
|
||||
# Print all underlying crypt devices of a block device |
||||
# print nothing if device is not on top of a crypt device |
||||
# $1: the block device to be checked in maj:min format |
||||
get_luks_crypt_dev() |
||||
{ |
||||
local _type |
||||
|
||||
[[ -b /dev/block/$1 ]] || return 1 |
||||
|
||||
_type=$(eval "$(blkid -u filesystem,crypto -o export -- "/dev/block/$1"); echo \$TYPE") |
||||
[[ $_type == "crypto_LUKS" ]] && echo "$1" |
||||
|
||||
for _x in "/sys/dev/block/$1/slaves/"*; do |
||||
[[ -f $_x/dev ]] || continue |
||||
[[ $_x/subsystem -ef /sys/class/block ]] || continue |
||||
get_luks_crypt_dev "$(< "$_x/dev")" |
||||
done |
||||
} |
||||
|
||||
# kdump_get_maj_min <device> |
||||
# Prints the major and minor of a device node. |
||||
# Example: |
||||
# $ get_maj_min /dev/sda2 |
||||
# 8:2 |
||||
kdump_get_maj_min() |
||||
{ |
||||
local _majmin |
||||
_majmin="$(stat -L -c '%t:%T' "$1" 2> /dev/null)" |
||||
printf "%s" "$((0x${_majmin%:*})):$((0x${_majmin#*:}))" |
||||
} |
||||
|
||||
get_all_kdump_crypt_dev() |
||||
{ |
||||
local _dev |
||||
|
||||
for _dev in $(get_block_dump_target); do |
||||
get_luks_crypt_dev "$(kdump_get_maj_min "$_dev")" |
||||
done |
||||
} |
||||
|
||||
check_vmlinux() |
||||
{ |
||||
# Use readelf to check if it's a valid ELF |
||||
readelf -h "$1" &> /dev/null || return 1 |
||||
} |
||||
|
||||
get_vmlinux_size() |
||||
{ |
||||
local size=0 _msize |
||||
|
||||
while read -r _msize; do |
||||
size=$((size + _msize)) |
||||
done <<< "$(readelf -l -W "$1" | awk '/^ LOAD/{print $6}' 2> /dev/stderr)" |
||||
|
||||
echo $size |
||||
} |
||||
|
||||
try_decompress() |
||||
{ |
||||
# The obscure use of the "tr" filter is to work around older versions of |
||||
# "grep" that report the byte offset of the line instead of the pattern. |
||||
|
||||
# Try to find the header ($1) and decompress from here |
||||
for pos in $(tr "$1\n$2" "\n$2=" < "$4" | grep -abo "^$2"); do |
||||
if ! type -P "$3" > /dev/null; then |
||||
ddebug "Signiature detected but '$3' is missing, skip this decompressor" |
||||
break |
||||
fi |
||||
|
||||
pos=${pos%%:*} |
||||
tail "-c+$pos" "$img" | $3 > "$5" 2> /dev/null |
||||
if check_vmlinux "$5"; then |
||||
ddebug "Kernel is extracted with '$3'" |
||||
return 0 |
||||
fi |
||||
done |
||||
|
||||
return 1 |
||||
} |
||||
|
||||
# Borrowed from linux/scripts/extract-vmlinux |
||||
get_kernel_size() |
||||
{ |
||||
# Prepare temp files: |
||||
local tmp img=$1 |
||||
|
||||
tmp=$(mktemp /tmp/vmlinux-XXX) |
||||
trap 'rm -f "$tmp"' 0 |
||||
|
||||
# Try to check if it's a vmlinux already |
||||
check_vmlinux "$img" && get_vmlinux_size "$img" && return 0 |
||||
|
||||
# That didn't work, so retry after decompression. |
||||
try_decompress '\037\213\010' xy gunzip "$img" "$tmp" || |
||||
try_decompress '\3757zXZ\000' abcde unxz "$img" "$tmp" || |
||||
try_decompress 'BZh' xy bunzip2 "$img" "$tmp" || |
||||
try_decompress '\135\0\0\0' xxx unlzma "$img" "$tmp" || |
||||
try_decompress '\211\114\132' xy 'lzop -d' "$img" "$tmp" || |
||||
try_decompress '\002!L\030' xxx 'lz4 -d' "$img" "$tmp" || |
||||
try_decompress '(\265/\375' xxx unzstd "$img" "$tmp" |
||||
|
||||
# Finally check for uncompressed images or objects: |
||||
[[ $? -eq 0 ]] && get_vmlinux_size "$tmp" && return 0 |
||||
|
||||
# Fallback to use iomem |
||||
local _size=0 _seg |
||||
while read -r _seg; do |
||||
_size=$((_size + 0x${_seg#*-} - 0x${_seg%-*})) |
||||
done <<< "$(grep -E "Kernel (code|rodata|data|bss)" /proc/iomem | cut -d ":" -f 1)" |
||||
echo $_size |
||||
} |
||||
@ -0,0 +1,355 @@
@@ -0,0 +1,355 @@
|
||||
#!/bin/sh |
||||
# |
||||
# This comes from the dracut-logger.sh |
||||
# |
||||
# The logger defined 4 logging levels: |
||||
# - ddebug (4) |
||||
# The DEBUG Level designates fine-grained informational events that are most |
||||
# useful to debug an application. |
||||
# - dinfo (3) |
||||
# The INFO level designates informational messages that highlight the |
||||
# progress of the application at coarse-grained level. |
||||
# - dwarn (2) |
||||
# The WARN level designates potentially harmful situations. |
||||
# - derror (1) |
||||
# The ERROR level designates error events that might still allow the |
||||
# application to continue running. |
||||
# |
||||
# Logging is controlled by following global variables: |
||||
# - @var kdump_stdloglvl - logging level to standard error (console output) |
||||
# - @var kdump_sysloglvl - logging level to syslog (by logger command) |
||||
# - @var kdump_kmsgloglvl - logging level to /dev/kmsg (only for boot-time) |
||||
# |
||||
# If any of the variables is not set, the function dlog_init() sets it to default: |
||||
# - In the first kernel: |
||||
# - @var kdump_stdloglvl = 3 (info) |
||||
# - @var kdump_sysloglvl = 0 (no logging) |
||||
# - @var kdump_kmsgloglvl = 0 (no logging) |
||||
# |
||||
# -In the second kernel: |
||||
# - @var kdump_stdloglvl = 0 (no logging) |
||||
# - @var kdump_sysloglvl = 3 (info) |
||||
# - @var kdump_kmsgloglvl = 0 (no logging) |
||||
# |
||||
# First of all you have to start with dlog_init() function which initializes |
||||
# required variables. Don't call any other logging function before that one! |
||||
# |
||||
# The code in this file might be run in an environment without bash. |
||||
# Any code added must be POSIX compliant. |
||||
|
||||
# Define vairables for the log levels in this module. |
||||
kdump_stdloglvl="" |
||||
kdump_sysloglvl="" |
||||
kdump_kmsgloglvl="" |
||||
|
||||
# The dracut-lib.sh is only available in the second kernel, and it won't |
||||
# be used in the first kernel because the dracut-lib.sh is invisible in |
||||
# the first kernel. |
||||
if [ -f /lib/dracut-lib.sh ]; then |
||||
. /lib/dracut-lib.sh |
||||
fi |
||||
|
||||
# @brief Get the log level from kernel command line. |
||||
# @retval 1 if something has gone wrong |
||||
# @retval 0 on success. |
||||
# |
||||
get_kdump_loglvl() |
||||
{ |
||||
[ -f /lib/dracut-lib.sh ] && kdump_sysloglvl=$(getarg rd.kdumploglvl) |
||||
[ -z "$kdump_sysloglvl" ] && return 1; |
||||
|
||||
if [ -f /lib/dracut-lib.sh ] && ! isdigit "$kdump_sysloglvl"; then |
||||
return 1 |
||||
fi |
||||
|
||||
return 0 |
||||
} |
||||
|
||||
# @brief Check the log level. |
||||
# @retval 1 if something has gone wrong |
||||
# @retval 0 on success. |
||||
# |
||||
check_loglvl() |
||||
{ |
||||
case "$1" in |
||||
0|1|2|3|4) |
||||
return 0 |
||||
;; |
||||
*) |
||||
return 1 |
||||
;; |
||||
esac |
||||
} |
||||
|
||||
# @brief Initializes Logger. |
||||
# @retval 1 if something has gone wrong |
||||
# @retval 0 on success. |
||||
# |
||||
dlog_init() { |
||||
ret=0 |
||||
|
||||
if [ -s /proc/vmcore ];then |
||||
if ! get_kdump_loglvl; then |
||||
logger -t "kdump[$$]" -p warn -- "Kdump is using the default log level(3)." |
||||
kdump_sysloglvl=3 |
||||
fi |
||||
kdump_stdloglvl=0 |
||||
kdump_kmsgloglvl=0 |
||||
else |
||||
kdump_stdloglvl=$KDUMP_STDLOGLVL |
||||
kdump_sysloglvl=$KDUMP_SYSLOGLVL |
||||
kdump_kmsgloglvl=$KDUMP_KMSGLOGLVL |
||||
fi |
||||
|
||||
[ -z "$kdump_stdloglvl" ] && kdump_stdloglvl=3 |
||||
[ -z "$kdump_sysloglvl" ] && kdump_sysloglvl=0 |
||||
[ -z "$kdump_kmsgloglvl" ] && kdump_kmsgloglvl=0 |
||||
|
||||
for loglvl in "$kdump_stdloglvl" "$kdump_kmsgloglvl" "$kdump_sysloglvl"; do |
||||
if ! check_loglvl "$loglvl"; then |
||||
echo "Illegal log level: $kdump_stdloglvl $kdump_kmsgloglvl $kdump_sysloglvl" |
||||
return 1 |
||||
fi |
||||
done |
||||
|
||||
# Skip initialization if it's already done. |
||||
[ -n "$kdump_maxloglvl" ] && return 0 |
||||
|
||||
if [ "$UID" -ne 0 ]; then |
||||
kdump_kmsgloglvl=0 |
||||
kdump_sysloglvl=0 |
||||
fi |
||||
|
||||
if [ "$kdump_sysloglvl" -gt 0 ]; then |
||||
if [ -d /run/systemd/journal ] \ |
||||
&& systemd-cat --version 1>/dev/null 2>&1 \ |
||||
&& systemctl --quiet is-active systemd-journald.socket 1>/dev/null 2>&1; then |
||||
readonly _systemdcatfile="/var/tmp/systemd-cat" |
||||
mkfifo "$_systemdcatfile" 1>/dev/null 2>&1 |
||||
readonly _dlogfd=15 |
||||
systemd-cat -t 'kdump' --level-prefix=true <"$_systemdcatfile" & |
||||
exec 15>"$_systemdcatfile" |
||||
elif ! [ -S /dev/log ] && [ -w /dev/log ] || ! command -v logger >/dev/null; then |
||||
# We cannot log to syslog, so turn this facility off. |
||||
kdump_kmsgloglvl=$kdump_sysloglvl |
||||
kdump_sysloglvl=0 |
||||
ret=1 |
||||
errmsg="No '/dev/log' or 'logger' included for syslog logging" |
||||
fi |
||||
fi |
||||
|
||||
kdump_maxloglvl=0 |
||||
for _dlog_lvl in $kdump_stdloglvl $kdump_sysloglvl $kdump_kmsgloglvl; do |
||||
[ $_dlog_lvl -gt $kdump_maxloglvl ] && kdump_maxloglvl=$_dlog_lvl |
||||
done |
||||
readonly kdump_maxloglvl |
||||
export kdump_maxloglvl |
||||
|
||||
if [ $kdump_stdloglvl -lt 4 ] && [ $kdump_kmsgloglvl -lt 4 ] && [ $kdump_sysloglvl -lt 4 ]; then |
||||
unset ddebug |
||||
ddebug() { :; }; |
||||
fi |
||||
|
||||
if [ $kdump_stdloglvl -lt 3 ] && [ $kdump_kmsgloglvl -lt 3 ] && [ $kdump_sysloglvl -lt 3 ]; then |
||||
unset dinfo |
||||
dinfo() { :; }; |
||||
fi |
||||
|
||||
if [ $kdump_stdloglvl -lt 2 ] && [ $kdump_kmsgloglvl -lt 2 ] && [ $kdump_sysloglvl -lt 2 ]; then |
||||
unset dwarn |
||||
dwarn() { :; }; |
||||
unset dwarning |
||||
dwarning() { :; }; |
||||
fi |
||||
|
||||
if [ $kdump_stdloglvl -lt 1 ] && [ $kdump_kmsgloglvl -lt 1 ] && [ $kdump_sysloglvl -lt 1 ]; then |
||||
unset derror |
||||
derror() { :; }; |
||||
fi |
||||
|
||||
[ -n "$errmsg" ] && derror "$errmsg" |
||||
|
||||
return $ret |
||||
} |
||||
|
||||
## @brief Converts numeric level to logger priority defined by POSIX.2. |
||||
# |
||||
# @param $1: Numeric logging level in range from 1 to 4. |
||||
# @retval 1 if @a lvl is out of range. |
||||
# @retval 0 if @a lvl is correct. |
||||
# @result Echoes logger priority. |
||||
_lvl2syspri() { |
||||
case "$1" in |
||||
1) echo error;; |
||||
2) echo warning;; |
||||
3) echo info;; |
||||
4) echo debug;; |
||||
*) return 1;; |
||||
esac |
||||
} |
||||
|
||||
## @brief Converts logger numeric level to syslog log level |
||||
# |
||||
# @param $1: Numeric logging level in range from 1 to 4. |
||||
# @retval 1 if @a lvl is out of range. |
||||
# @retval 0 if @a lvl is correct. |
||||
# @result Echoes kernel console numeric log level |
||||
# |
||||
# Conversion is done as follows: |
||||
# |
||||
# <tt> |
||||
# none -> LOG_EMERG (0) |
||||
# none -> LOG_ALERT (1) |
||||
# none -> LOG_CRIT (2) |
||||
# ERROR(1) -> LOG_ERR (3) |
||||
# WARN(2) -> LOG_WARNING (4) |
||||
# none -> LOG_NOTICE (5) |
||||
# INFO(3) -> LOG_INFO (6) |
||||
# DEBUG(4) -> LOG_DEBUG (7) |
||||
# </tt> |
||||
# |
||||
# @see /usr/include/sys/syslog.h |
||||
_dlvl2syslvl() { |
||||
case "$1" in |
||||
1) set -- 3;; |
||||
2) set -- 4;; |
||||
3) set -- 6;; |
||||
4) set -- 7;; |
||||
*) return 1;; |
||||
esac |
||||
|
||||
# The number is constructed by multiplying the facility by 8 and then |
||||
# adding the level. |
||||
# About The Syslog Protocol, please refer to the RFC5424 for more details. |
||||
echo $((24 + $1)) |
||||
} |
||||
|
||||
## @brief Prints to stderr, to syslog and/or /dev/kmsg given message with |
||||
# given level (priority). |
||||
# |
||||
# @param $1: Numeric logging level. |
||||
# @param $2: Message. |
||||
# @retval 0 It's always returned, even if logging failed. |
||||
# |
||||
# @note This function is not supposed to be called manually. Please use |
||||
# dinfo(), ddebug(), or others instead which wrap this one. |
||||
# |
||||
# This is core logging function which logs given message to standard error |
||||
# and/or syslog (with POSIX shell command <tt>logger</tt>) and/or to /dev/kmsg. |
||||
# The format is following: |
||||
# |
||||
# <tt>X: some message</tt> |
||||
# |
||||
# where @c X is the first letter of logging level. See module description for |
||||
# details on that. |
||||
# |
||||
# Message to syslog is sent with tag @c kdump. Priorities are mapped as |
||||
# following: |
||||
# - @c ERROR to @c error |
||||
# - @c WARN to @c warning |
||||
# - @c INFO to @c info |
||||
# - @c DEBUG to @c debug |
||||
_do_dlog() { |
||||
[ "$1" -le $kdump_stdloglvl ] && printf -- 'kdump: %s\n' "$2" >&2 |
||||
|
||||
if [ "$1" -le $kdump_sysloglvl ]; then |
||||
if [ "$_dlogfd" ]; then |
||||
printf -- "<%s>%s\n" "$(($(_dlvl2syslvl "$1") & 7))" "$2" 1>&$_dlogfd |
||||
else |
||||
logger -t "kdump[$$]" -p "$(_lvl2syspri "$1")" -- "$2" |
||||
fi |
||||
fi |
||||
|
||||
[ "$1" -le $kdump_kmsgloglvl ] && \ |
||||
echo "<$(_dlvl2syslvl "$1")>kdump[$$] $2" >/dev/kmsg |
||||
} |
||||
|
||||
## @brief Internal helper function for _do_dlog() |
||||
# |
||||
# @param $1: Numeric logging level. |
||||
# @param $2 [...]: Message. |
||||
# @retval 0 It's always returned, even if logging failed. |
||||
# |
||||
# @note This function is not supposed to be called manually. Please use |
||||
# dinfo(), ddebug(), or others instead which wrap this one. |
||||
# |
||||
# This function calls _do_dlog() either with parameter msg, or if |
||||
# none is given, it will read standard input and will use every line as |
||||
# a message. |
||||
# |
||||
# This enables: |
||||
# dwarn "This is a warning" |
||||
# echo "This is a warning" | dwarn |
||||
dlog() { |
||||
[ -z "$kdump_maxloglvl" ] && return 0 |
||||
[ "$1" -le "$kdump_maxloglvl" ] || return 0 |
||||
|
||||
if [ $# -gt 1 ]; then |
||||
_dlog_lvl=$1; shift |
||||
_do_dlog "$_dlog_lvl" "$*" |
||||
else |
||||
while read -r line || [ -n "$line" ]; do |
||||
_do_dlog "$1" "$line" |
||||
done |
||||
fi |
||||
} |
||||
|
||||
## @brief Logs message at DEBUG level (4) |
||||
# |
||||
# @param msg Message. |
||||
# @retval 0 It's always returned, even if logging failed. |
||||
ddebug() { |
||||
set +x |
||||
dlog 4 "$@" |
||||
if [ -n "$debug" ]; then |
||||
set -x |
||||
fi |
||||
} |
||||
|
||||
## @brief Logs message at INFO level (3) |
||||
# |
||||
# @param msg Message. |
||||
# @retval 0 It's always returned, even if logging failed. |
||||
dinfo() { |
||||
set +x |
||||
dlog 3 "$@" |
||||
if [ -n "$debug" ]; then |
||||
set -x |
||||
fi |
||||
} |
||||
|
||||
## @brief Logs message at WARN level (2) |
||||
# |
||||
# @param msg Message. |
||||
# @retval 0 It's always returned, even if logging failed. |
||||
dwarn() { |
||||
set +x |
||||
dlog 2 "$@" |
||||
if [ -n "$debug" ]; then |
||||
set -x |
||||
fi |
||||
} |
||||
|
||||
## @brief It's an alias to dwarn() function. |
||||
# |
||||
# @param msg Message. |
||||
# @retval 0 It's always returned, even if logging failed. |
||||
dwarning() { |
||||
set +x |
||||
dwarn "$@" |
||||
if [ -n "$debug" ]; then |
||||
set -x |
||||
fi |
||||
} |
||||
|
||||
## @brief Logs message at ERROR level (1) |
||||
# |
||||
# @param msg Message. |
||||
# @retval 0 It's always returned, even if logging failed. |
||||
derror() { |
||||
set +x |
||||
dlog 1 "$@" |
||||
if [ -n "$debug" ]; then |
||||
set -x |
||||
fi |
||||
} |
||||
@ -0,0 +1,8 @@
@@ -0,0 +1,8 @@
|
||||
#!/bin/sh |
||||
|
||||
systemctl is-active kdump |
||||
if [ $? -ne 0 ]; then |
||||
exit 0 |
||||
fi |
||||
|
||||
/usr/lib/kdump/kdump-restart.sh |
||||
@ -0,0 +1,8 @@
@@ -0,0 +1,8 @@
|
||||
#!/bin/bash |
||||
export PATH="$PATH:/usr/bin:/usr/sbin" |
||||
|
||||
exec >>/var/log/kdump-migration.log 2>&1 |
||||
|
||||
echo "kdump: Partition Migration detected. Rebuilding initramfs image to reload." |
||||
/usr/bin/kdumpctl rebuild |
||||
/usr/bin/kdumpctl reload |
||||
@ -0,0 +1,42 @@
@@ -0,0 +1,42 @@
|
||||
#!/bin/bash |
||||
# This util helps to reduce the workload of kdump service restarting |
||||
# on udev event. When hotplugging memory / CPU, multiple udev |
||||
# events may be triggered concurrently, and obviously, we don't want |
||||
# to restart kdump service for each event. |
||||
|
||||
# This script will be called by udev, and make sure kdump service is |
||||
# restart after all events we are watching are settled. |
||||
|
||||
# On each call, this script will update try to aquire the $throttle_lock |
||||
# The first instance acquired the file lock will keep waiting for events |
||||
# to settle and then reload kdump. Other instances will just exit |
||||
# In this way, we can make sure kdump service is restarted immediately |
||||
# and for exactly once after udev events are settled. |
||||
|
||||
throttle_lock="/var/lock/kdump-udev-throttle" |
||||
|
||||
exec 9>$throttle_lock |
||||
if [ $? -ne 0 ]; then |
||||
echo "Failed to create the lock file! Fallback to non-throttled kdump service restart" |
||||
/bin/kdumpctl reload |
||||
exit 1 |
||||
fi |
||||
|
||||
flock -n 9 |
||||
if [ $? -ne 0 ]; then |
||||
echo "Throttling kdump restart for concurrent udev event" |
||||
exit 0 |
||||
fi |
||||
|
||||
# Wait for at least 1 second, at most 4 seconds for udev to settle |
||||
# Idealy we will have a less than 1 second lag between udev events settle |
||||
# and kdump reload |
||||
sleep 1 && udevadm settle --timeout 3 |
||||
|
||||
# Release the lock, /bin/kdumpctl will block and make the process |
||||
# holding two locks at the same time and we might miss some events |
||||
exec 9>&- |
||||
|
||||
/bin/kdumpctl reload |
||||
|
||||
exit 0 |
||||
@ -0,0 +1,192 @@
@@ -0,0 +1,192 @@
|
||||
# This file contains a series of commands to perform (in order) in the kdump |
||||
# kernel after a kernel crash in the crash kernel(1st kernel) has happened. |
||||
# |
||||
# Directives in this file are only applicable to the kdump initramfs, and have |
||||
# no effect once the root filesystem is mounted and the normal init scripts are |
||||
# processed. |
||||
# |
||||
# Currently, only one dump target and path can be specified. If the dumping to |
||||
# the configured target fails, the failure action which can be configured via |
||||
# the "failure_action" directive will be performed. |
||||
# |
||||
# Supported options: |
||||
# |
||||
# auto_reset_crashkernel <yes|no> |
||||
# - whether to reset kernel crashkernel to new default value |
||||
# or not when kexec-tools updates the default crashkernel value and |
||||
# existing kernels using the old default kernel crashkernel value. |
||||
# The default value is yes. |
||||
# |
||||
# raw <partition> |
||||
# - Will dd /proc/vmcore into <partition>. |
||||
# Use persistent device names for partition devices, |
||||
# such as /dev/vg/<devname>. |
||||
# |
||||
# nfs <nfs mount> |
||||
# - Will mount nfs to <mnt>, and copy /proc/vmcore to |
||||
# <mnt>/<path>/%HOST-%DATE/, supports DNS. |
||||
# |
||||
# ssh <user@server> |
||||
# - Will save /proc/vmcore to <user@server>:<path>/%HOST-%DATE/, |
||||
# supports DNS. |
||||
# NOTE: make sure the user has write permissions on the server. |
||||
# |
||||
# sshkey <path> |
||||
# - Will use the sshkey to do ssh dump. |
||||
# Specify the path of the ssh key to use when dumping |
||||
# via ssh. The default value is /root/.ssh/kdump_id_rsa. |
||||
# |
||||
# <fs type> <partition> |
||||
# - Will mount -t <fs type> <partition> <mnt>, and copy |
||||
# /proc/vmcore to <mnt>/<path>/%HOST_IP-%DATE/. |
||||
# NOTE: <partition> can be a device node, label or uuid. |
||||
# It's recommended to use persistent device names |
||||
# such as /dev/vg/<devname>. |
||||
# Otherwise it's suggested to use label or uuid. |
||||
# |
||||
# path <path> |
||||
# - "path" represents the file system path in which vmcore |
||||
# will be saved. If a dump target is specified in |
||||
# kdump.conf, then "path" is relative to the specified |
||||
# dump target. |
||||
# |
||||
# Interpretation of "path" changes a bit if the user didn't |
||||
# specify any dump target explicitly in kdump.conf. In this |
||||
# case, "path" represents the absolute path from root. The |
||||
# dump target and adjusted path are arrived at automatically |
||||
# depending on what's mounted in the current system. |
||||
# |
||||
# Ignored for raw device dumps. If unset, will use the default |
||||
# "/var/crash". |
||||
# |
||||
# core_collector <command> <options> |
||||
# - This allows you to specify the command to copy |
||||
# the vmcore. The default is makedumpfile, which on |
||||
# some architectures can drastically reduce vmcore size. |
||||
# See /sbin/makedumpfile --help for a list of options. |
||||
# Note that the -i and -g options are not needed here, |
||||
# as the initrd will automatically be populated with a |
||||
# config file appropriate for the running kernel. |
||||
# The default core_collector for raw/ssh dump is: |
||||
# "makedumpfile -F -l --message-level 7 -d 31". |
||||
# The default core_collector for other targets is: |
||||
# "makedumpfile -l --message-level 7 -d 31". |
||||
# |
||||
# "makedumpfile -F" will create a flattened vmcore. |
||||
# You need to use "makedumpfile -R" to rearrange the dump data to |
||||
# a normal dumpfile readable with analysis tools. For example: |
||||
# "makedumpfile -R vmcore < vmcore.flat". |
||||
# |
||||
# For core_collector format details, you can refer to |
||||
# kexec-kdump-howto.txt or kdump.conf manpage. |
||||
# |
||||
# kdump_post <binary | script> |
||||
# - This directive allows you to run a executable binary |
||||
# or script after the vmcore dump process terminates. |
||||
# The exit status of the current dump process is fed to |
||||
# the executable binary or script as its first argument. |
||||
# All files under /etc/kdump/post.d are collectively sorted |
||||
# and executed in lexical order, before binary or script |
||||
# specified kdump_post parameter is executed. |
||||
# |
||||
# kdump_pre <binary | script> |
||||
# - Works like the "kdump_post" directive, but instead of running |
||||
# after the dump process, runs immediately before it. |
||||
# Exit status of this binary is interpreted as follows: |
||||
# 0 - continue with dump process as usual |
||||
# non 0 - run the final action (reboot/poweroff/halt) |
||||
# All files under /etc/kdump/pre.d are collectively sorted and |
||||
# executed in lexical order, after binary or script specified |
||||
# kdump_pre parameter is executed. |
||||
# Even if the binary or script in /etc/kdump/pre.d directory |
||||
# returns non 0 exit status, the processing is continued. |
||||
# |
||||
# extra_bins <binaries | shell scripts> |
||||
# - This directive allows you to specify additional binaries or |
||||
# shell scripts to be included in the kdump initrd. |
||||
# Generally they are useful in conjunction with a kdump_post |
||||
# or kdump_pre binary or script which depends on these extra_bins. |
||||
# |
||||
# extra_modules <module(s)> |
||||
# - This directive allows you to specify extra kernel modules |
||||
# that you want to be loaded in the kdump initrd. |
||||
# Multiple modules can be listed, separated by spaces, and any |
||||
# dependent modules will automatically be included. |
||||
# |
||||
# failure_action <reboot | halt | poweroff | shell | dump_to_rootfs> |
||||
# - Action to perform in case dumping fails. |
||||
# reboot: Reboot the system. |
||||
# halt: Halt the system. |
||||
# poweroff: Power down the system. |
||||
# shell: Drop to a bash shell. |
||||
# Exiting the shell reboots the system by default, |
||||
# or perform "final_action". |
||||
# dump_to_rootfs: Dump vmcore to rootfs from initramfs context and |
||||
# reboot by default or perform "final_action". |
||||
# Useful when non-root dump target is specified. |
||||
# The default option is "reboot". |
||||
# |
||||
# default <reboot | halt | poweroff | shell | dump_to_rootfs> |
||||
# - Same as the "failure_action" directive above, but this directive |
||||
# is obsolete and will be removed in the future. |
||||
# |
||||
# final_action <reboot | halt | poweroff> |
||||
# - Action to perform in case dumping succeeds. Also performed |
||||
# when "shell" or "dump_to_rootfs" failure action finishes. |
||||
# Each action is same as the "failure_action" directive above. |
||||
# The default is "reboot". |
||||
# |
||||
# force_rebuild <0 | 1> |
||||
# - By default, kdump initrd will only be rebuilt when necessary. |
||||
# Specify 1 to force rebuilding kdump initrd every time when kdump |
||||
# service starts. |
||||
# |
||||
# force_no_rebuild <0 | 1> |
||||
# - By default, kdump initrd will be rebuilt when necessary. |
||||
# Specify 1 to bypass rebuilding of kdump initrd. |
||||
# |
||||
# force_no_rebuild and force_rebuild options are mutually |
||||
# exclusive and they should not be set to 1 simultaneously. |
||||
# |
||||
# override_resettable <0 | 1> |
||||
# - Usually an unresettable block device can't be a dump target. |
||||
# Specifying 1 when you want to dump even though the block |
||||
# target is unresettable |
||||
# By default, it is 0, which will not try dumping destined to fail. |
||||
# |
||||
# dracut_args <arg(s)> |
||||
# - Pass extra dracut options when rebuilding kdump initrd. |
||||
# |
||||
# fence_kdump_args <arg(s)> |
||||
# - Command line arguments for fence_kdump_send (it can contain |
||||
# all valid arguments except hosts to send notification to). |
||||
# |
||||
# fence_kdump_nodes <node(s)> |
||||
# - List of cluster node(s) except localhost, separated by spaces, |
||||
# to send fence_kdump notifications to. |
||||
# (this option is mandatory to enable fence_kdump). |
||||
# |
||||
|
||||
#raw /dev/vg/lv_kdump |
||||
#ext4 /dev/vg/lv_kdump |
||||
#ext4 LABEL=/boot |
||||
#ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937 |
||||
#nfs my.server.com:/export/tmp |
||||
#nfs [2001:db8::1:2:3:4]:/export/tmp |
||||
#ssh user@my.server.com |
||||
#ssh user@2001:db8::1:2:3:4 |
||||
#sshkey /root/.ssh/kdump_id_rsa |
||||
auto_reset_crashkernel yes |
||||
path /var/crash |
||||
core_collector makedumpfile -l --message-level 7 -d 31 |
||||
#core_collector scp |
||||
#kdump_post /var/crash/scripts/kdump-post.sh |
||||
#kdump_pre /var/crash/scripts/kdump-pre.sh |
||||
#extra_bins /usr/bin/lftp |
||||
#extra_modules gfs2 |
||||
#failure_action shell |
||||
#force_rebuild 1 |
||||
#force_no_rebuild 1 |
||||
#dracut_args --omit-drivers "cfg80211 snd" --add-drivers "ext2 ext3" |
||||
#fence_kdump_args -p 7410 -f auto -c 0 -i 10 |
||||
#fence_kdump_nodes node1 node2 |
||||
@ -0,0 +1,387 @@
@@ -0,0 +1,387 @@
|
||||
.TH KDUMP.CONF 5 "07/23/2008" "kexec-tools" |
||||
|
||||
.SH NAME |
||||
kdump.conf \- configuration file for kdump kernel. |
||||
|
||||
.SH DESCRIPTION |
||||
|
||||
kdump.conf is a configuration file for the kdump kernel crash |
||||
collection service. |
||||
|
||||
kdump.conf provides post-kexec instructions to the kdump kernel. It is |
||||
stored in the initrd file managed by the kdump service. If you change |
||||
this file and do not want to reboot in order for the changes to take |
||||
effect, restart the kdump service to rebuild the initrd. |
||||
|
||||
For most configurations, you can simply review the examples provided |
||||
in the stock /etc/kdump.conf. |
||||
|
||||
.B NOTE: |
||||
For filesystem dumps the dump target must be mounted before building |
||||
kdump initramfs. |
||||
|
||||
kdump.conf only affects the behavior of the initramfs. Please read the |
||||
kdump operational flow section of kexec-kdump-howto.txt in the docs to better |
||||
understand how this configuration file affects the behavior of kdump. |
||||
|
||||
.SH OPTIONS |
||||
|
||||
.B auto_reset_crashkernel <yes|no> |
||||
.RS |
||||
determine whether to reset kernel crashkernel to new default value |
||||
or not when kexec-tools updates the default crashkernel value and |
||||
existing kernels using the old default kernel crashkernel value |
||||
|
||||
.B raw <partition> |
||||
.RS |
||||
Will dd /proc/vmcore into <partition>. Use persistent device names for |
||||
partition devices, such as /dev/vg/<devname>. |
||||
.RE |
||||
|
||||
.B nfs <nfs mount> |
||||
.RS |
||||
Will mount nfs to <mnt>, and copy /proc/vmcore to <mnt>/<path>/%HOST-%DATE/, |
||||
supports DNS. Note that a fqdn should be used as the server name in the |
||||
mount point. |
||||
.RE |
||||
|
||||
.B ssh <user@server> |
||||
.RS |
||||
Will save /proc/vmcore through ssh pipe to <user@server>:<path>/%HOST-%DATE/, |
||||
supports DNS. NOTE: make sure user has necessary write permissions on |
||||
server and that a fqdn is used as the server name. |
||||
.RE |
||||
|
||||
.B sshkey <path> |
||||
.RS |
||||
Specify the path of the ssh key to use when dumping via ssh. |
||||
The default value is /root/.ssh/kdump_id_rsa. |
||||
.RE |
||||
|
||||
.B <fs type> <partition> |
||||
.RS |
||||
Will mount -t <fs type> <partition> <mnt>, and copy /proc/vmcore to |
||||
<mnt>/<path>/%HOST_IP-%DATE/. NOTE: <partition> can be a device node, label |
||||
or uuid. It's recommended to use persistent device names such as |
||||
/dev/vg/<devname>. Otherwise it's suggested to use label or uuid. |
||||
.RE |
||||
|
||||
.B path <path> |
||||
.RS |
||||
"path" represents the file system path in which vmcore will be saved. |
||||
If a dump target is specified in kdump.conf, then "path" is relative to the |
||||
specified dump target. |
||||
.PP |
||||
Interpretation of "path" changes a bit if the user didn't specify any dump |
||||
target explicitly in kdump.conf. In this case, "path" represents the |
||||
absolute path from root. The dump target and adjusted path are arrived |
||||
at automatically depending on what's mounted in the current system. |
||||
.PP |
||||
Ignored for raw device dumps. If unset, will use the default "/var/crash". |
||||
.RE |
||||
|
||||
.B core_collector <command> <options> |
||||
.RS |
||||
This allows you to specify the command to copy the vmcore. |
||||
The default is makedumpfile, which on some architectures can drastically reduce |
||||
core file size. See /sbin/makedumpfile --help for a list of options. |
||||
Note that the -i and -g options are not needed here, as the initrd |
||||
will automatically be populated with a config file appropriate |
||||
for the running kernel. |
||||
.PP |
||||
Note 1: About default core collector: |
||||
The default core_collector for raw/ssh dump is: |
||||
"makedumpfile -F -l --message-level 7 -d 31". |
||||
The default core_collector for other targets is: |
||||
"makedumpfile -l --message-level 7 -d 31". |
||||
Even if core_collector option is commented out in kdump.conf, makedumpfile |
||||
is the default core collector and kdump uses it internally. |
||||
If one does not want makedumpfile as default core_collector, then they |
||||
need to specify one using core_collector option to change the behavior. |
||||
.PP |
||||
Note 2: If "makedumpfile -F" is used then you will get a flattened format |
||||
vmcore.flat, you will need to use "makedumpfile -R" to rearrange the |
||||
dump data from standard input to a normal dumpfile (readable with analysis |
||||
tools). |
||||
ie. "makedumpfile -R vmcore < vmcore.flat" |
||||
.PP |
||||
Note 3: If specified core_collector simply copy the vmcore file to the |
||||
dump target (eg: cp, scp), the vmcore could be significantly large. |
||||
Please make sure the dump target has enough space, at leaset larger |
||||
than the system's RAM. |
||||
|
||||
.RE |
||||
|
||||
.B kdump_post <binary | script> |
||||
.RS |
||||
This directive allows you to run a specified executable |
||||
just after the vmcore dump process terminates. The exit |
||||
status of the current dump process is fed to the kdump_post |
||||
executable as its first argument($1). Executable can modify |
||||
it to indicate the new exit status of succeeding dump process, |
||||
.PP |
||||
All files under /etc/kdump/post.d are collectively sorted |
||||
and executed in lexical order, before binary or script |
||||
specified kdump_post parameter is executed. |
||||
.PP |
||||
Note that scripts written for use with this directive must use the /bin/bash |
||||
interpreter. And since these scripts run in kdump enviroment, the reference to |
||||
the storage or network device in the scripts should adhere to the section |
||||
'Supported dump target types and requirements' in kexec-kdump-howto.txt. |
||||
|
||||
.RE |
||||
|
||||
.B kdump_pre <binary | script> |
||||
.RS |
||||
Works just like the "kdump_post" directive, but instead |
||||
of running after the dump process, runs immediately |
||||
before. Exit status of this binary is interpreted |
||||
as follows: |
||||
.PP |
||||
0 - continue with dump process as usual |
||||
.PP |
||||
non 0 - run the final action (reboot/poweroff/halt) |
||||
.PP |
||||
All files under /etc/kdump/pre.d are collectively sorted and |
||||
executed in lexical order, after binary or script specified |
||||
kdump_pre parameter is executed. |
||||
Even if the binary or script in /etc/kdump/pre.d directory |
||||
returns non 0 exit status, the processing is continued. |
||||
.PP |
||||
Note that scripts written for use with this directive must use the /bin/bash |
||||
interpreter. And since these scripts run in kdump enviroment, the reference to |
||||
the storage or network device in the scripts should adhere to the section |
||||
'Supported dump target types and requirements' in kexec-kdump-howto.txt. |
||||
|
||||
.RE |
||||
|
||||
.B extra_bins <binaries | shell scripts> |
||||
.RS |
||||
This directive allows you to specify additional |
||||
binaries or shell scripts you'd like to include in |
||||
your kdump initrd. Generally only useful in |
||||
conjunction with a kdump_post binary or script that |
||||
relies on other binaries or scripts. |
||||
.RE |
||||
|
||||
.B extra_modules <module(s)> |
||||
.RS |
||||
This directive allows you to specify extra kernel |
||||
modules that you want to be loaded in the kdump |
||||
initrd, typically used to set up access to |
||||
non-boot-path dump targets that might otherwise |
||||
not be accessible in the kdump environment. Multiple |
||||
modules can be listed, separated by spaces, and any |
||||
dependent modules will automatically be included. |
||||
.RE |
||||
|
||||
.B failure_action <reboot | halt | poweroff | shell | dump_to_rootfs> |
||||
.RS |
||||
Action to perform in case dumping to the intended target fails. The default is "reboot". |
||||
reboot: Reboot the system (this is what most people will want, as it returns the system |
||||
to a normal state). halt: Halt the system and lose the vmcore. poweroff: The system |
||||
will be powered down. shell: Drop to a shell session inside the initramfs, from which |
||||
you can manually perform additional recovery actions. Exiting this shell reboots the |
||||
system by default or performs "final_action". |
||||
Note: kdump uses bash as the default shell. dump_to_rootfs: If non-root dump |
||||
target is specified, the failure action can be set as dump_to_rootfs. That means when |
||||
dumping to target fails, dump vmcore to rootfs from initramfs context and reboot |
||||
by default or perform "final_action". |
||||
.RE |
||||
|
||||
.B default <reboot | halt | poweroff | shell | dump_to_rootfs> |
||||
.RS |
||||
Same as the "failure_action" directive above, but this directive is obsolete |
||||
and will be removed in the future. |
||||
.RE |
||||
|
||||
.B final_action <reboot | halt | poweroff> |
||||
.RS |
||||
Action to perform in case dumping to the intended target succeeds. |
||||
Also performed when "shell" or "dump_to_rootfs" failure action finishes. |
||||
Each action is same as the "failure_action" directive above. |
||||
The default is "reboot". |
||||
.RE |
||||
|
||||
.B force_rebuild <0 | 1> |
||||
.RS |
||||
By default, kdump initrd will only be rebuilt when necessary. |
||||
Specify 1 to force rebuilding kdump initrd every time when kdump service starts. |
||||
.RE |
||||
|
||||
.B force_no_rebuild <0 | 1> |
||||
.RS |
||||
By default, kdump initrd will be rebuilt when necessary. |
||||
Specify 1 to bypass rebuilding of kdump initrd. |
||||
|
||||
.PP |
||||
force_no_rebuild and force_rebuild options are mutually exclusive and |
||||
they should not be set to 1 simultaneously. |
||||
.RE |
||||
|
||||
.B override_resettable <0 | 1> |
||||
.RS |
||||
Usually an unresettable block device can't be a dump target. Specifying 1 means |
||||
that even though the block target is unresettable, the user wants to try dumping anyway. |
||||
By default, it's set to 0, which will not try something destined to fail. |
||||
.RE |
||||
|
||||
|
||||
.B dracut_args <arg(s)> |
||||
.RS |
||||
Kdump uses dracut to generate initramfs for second kernel. This option |
||||
allows a user to pass arguments to dracut directly. |
||||
.RE |
||||
|
||||
|
||||
.B fence_kdump_args <arg(s)> |
||||
.RS |
||||
Command line arguments for fence_kdump_send (it can contain all valid |
||||
arguments except hosts to send notification to). |
||||
.RE |
||||
|
||||
|
||||
.B fence_kdump_nodes <node(s)> |
||||
.RS |
||||
List of cluster node(s) except localhost, separated by spaces, to send fence_kdump notification |
||||
to (this option is mandatory to enable fence_kdump). |
||||
.RE |
||||
|
||||
|
||||
.SH DEPRECATED OPTIONS |
||||
|
||||
.B net <nfs mount>|<user@server> |
||||
.RS |
||||
net option is replaced by nfs and ssh options. Use nfs or ssh options |
||||
directly. |
||||
.RE |
||||
|
||||
.B options <module> <option list> |
||||
.RS |
||||
Use KDUMP_COMMANDLINE_APPEND in /etc/sysconfig/kdump to add module options as |
||||
kernel command line parameters. For example, specify 'loop.max_loop=1' to limit |
||||
maximum loop devices to 1. |
||||
.RE |
||||
|
||||
.B link_delay <seconds> |
||||
.RS |
||||
link_delay was used to wait for a network device to initialize before using it. |
||||
Now dracut network module takes care of this issue automatically. |
||||
.RE |
||||
|
||||
.B disk_timeout <seconds> |
||||
.RS |
||||
Similar to link_delay, dracut ensures disks are ready before kdump uses them. |
||||
.RE |
||||
|
||||
.B debug_mem_level <0-3> |
||||
.RS |
||||
Turn on verbose debug output of kdump scripts regarding free/used memory at |
||||
various points of execution. This feature has been |
||||
moved to dracut now. |
||||
Use KDUMP_COMMANDLINE_APPEND in /etc/sysconfig/kdump and |
||||
append dracut cmdline param rd.memdebug=[0-3] to enable the debug output. |
||||
|
||||
Higher level means more debugging output. |
||||
.PP |
||||
0 - no output |
||||
.PP |
||||
1 - partial /proc/meminfo |
||||
.PP |
||||
2 - /proc/meminfo |
||||
.PP |
||||
3 - /proc/meminfo + /proc/slabinfo |
||||
.RE |
||||
|
||||
.B blacklist <list of kernel modules> |
||||
.RS |
||||
blacklist option was recently being used to prevent loading modules in |
||||
initramfs. General terminology for blacklist has been that module is |
||||
present in initramfs but it is not actually loaded in kernel. Hence |
||||
retaining blacklist option creates more confusing behavior. It has been |
||||
deprecated. |
||||
.PP |
||||
Instead, use rd.driver.blacklist option on second kernel to blacklist |
||||
a certain module. One can edit /etc/sysconfig/kdump.conf and edit |
||||
KDUMP_COMMANDLINE_APPEND to pass kernel command line options. Refer |
||||
to dracut.cmdline man page for more details on module blacklist option. |
||||
.RE |
||||
|
||||
.RE |
||||
|
||||
.SH EXAMPLES |
||||
Here are some examples for core_collector option: |
||||
.PP |
||||
Core collector command format depends on dump target type. Typically for |
||||
filesystem (local/remote), core_collector should accept two arguments. |
||||
First one is source file and second one is target file. For ex. |
||||
.TP |
||||
ex1. |
||||
core_collector "cp --sparse=always" |
||||
|
||||
Above will effectively be translated to: |
||||
|
||||
cp --sparse=always /proc/vmcore <dest-path>/vmcore |
||||
.TP |
||||
ex2. |
||||
core_collector "makedumpfile -l --message-level 7 -d 31" |
||||
|
||||
Above will effectively be translated to: |
||||
|
||||
makedumpfile -l --message-level 7 -d 31 /proc/vmcore <dest-path>/vmcore |
||||
.PP |
||||
For dump targets like raw and ssh, in general, core collector should expect |
||||
one argument (source file) and should output the processed core on standard |
||||
output (There is one exception of "scp", discussed later). This standard |
||||
output will be saved to destination using appropriate commands. |
||||
|
||||
raw dumps examples: |
||||
.TP |
||||
ex3. |
||||
core_collector "cat" |
||||
|
||||
Above will effectively be translated to. |
||||
|
||||
cat /proc/vmcore | dd of=<target-device> |
||||
.TP |
||||
ex4. |
||||
core_collector "makedumpfile -F -l --message-level 7 -d 31" |
||||
|
||||
Above will effectively be translated to. |
||||
|
||||
makedumpfile -F -l --message-level 7 -d 31 | dd of=<target-device> |
||||
.PP |
||||
ssh dumps examples |
||||
.TP |
||||
ex5. |
||||
core_collector "cat" |
||||
|
||||
Above will effectively be translated to. |
||||
|
||||
cat /proc/vmcore | ssh <options> <remote-location> "dd of=path/vmcore" |
||||
.TP |
||||
ex6. |
||||
core_collector "makedumpfile -F -l --message-level 7 -d 31" |
||||
|
||||
Above will effectively be translated to. |
||||
|
||||
makedumpfile -F -l --message-level 7 -d 31 | ssh <options> <remote-location> "dd of=path/vmcore" |
||||
|
||||
There is one exception to standard output rule for ssh dumps. And that is |
||||
scp. As scp can handle ssh destinations for file transfers, one can |
||||
specify "scp" as core collector for ssh targets (no output on stdout). |
||||
.TP |
||||
ex7. |
||||
core_collector "scp" |
||||
|
||||
Above will effectively be translated to. |
||||
|
||||
scp /proc/vmcore <user@host>:path/vmcore |
||||
|
||||
.PP |
||||
examples for other options please see |
||||
.I /etc/kdump.conf |
||||
|
||||
.SH SEE ALSO |
||||
|
||||
kexec(8) mkdumprd(8) dracut.cmdline(7) |
||||
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
[Unit] |
||||
Description=Crash recovery kernel arming |
||||
After=network.target network-online.target remote-fs.target basic.target |
||||
DefaultDependencies=no |
||||
ConditionKernelCommandLine=crashkernel |
||||
|
||||
[Service] |
||||
Type=oneshot |
||||
ExecStart=/usr/bin/kdumpctl start |
||||
ExecStop=/usr/bin/kdumpctl stop |
||||
ExecReload=/usr/bin/kdumpctl reload |
||||
RemainAfterExit=yes |
||||
StartLimitInterval=0 |
||||
|
||||
[Install] |
||||
WantedBy=multi-user.target |
||||
@ -0,0 +1,53 @@
@@ -0,0 +1,53 @@
|
||||
# Kernel Version string for the -kdump kernel, such as 2.6.13-1544.FC5kdump |
||||
# If no version is specified, then the init script will try to find a |
||||
# kdump kernel with the same version number as the running kernel. |
||||
KDUMP_KERNELVER="" |
||||
|
||||
# The kdump commandline is the command line that needs to be passed off to |
||||
# the kdump kernel. This will likely match the contents of the grub kernel |
||||
# line. For example: |
||||
# KDUMP_COMMANDLINE="ro root=LABEL=/" |
||||
# Dracut depends on proper root= options, so please make sure that appropriate |
||||
# root= options are copied from /proc/cmdline. In general it is best to append |
||||
# command line options using "KDUMP_COMMANDLINE_APPEND=". |
||||
# If a command line is not specified, the default will be taken from |
||||
# /proc/cmdline |
||||
KDUMP_COMMANDLINE="" |
||||
|
||||
# This variable lets us remove arguments from the current kdump commandline |
||||
# as taken from either KDUMP_COMMANDLINE above, or from /proc/cmdline |
||||
# NOTE: some arguments such as crashkernel will always be removed |
||||
KDUMP_COMMANDLINE_REMOVE="hugepages hugepagesz slub_debug quiet log_buf_len swiotlb cma hugetlb_cma" |
||||
|
||||
# This variable lets us append arguments to the current kdump commandline |
||||
# after processed by KDUMP_COMMANDLINE_REMOVE |
||||
KDUMP_COMMANDLINE_APPEND="irqpoll maxcpus=1 reset_devices novmcoredd cma=0 hugetlb_cma=0" |
||||
|
||||
# Any additional kexec arguments required. In most situations, this should |
||||
# be left empty |
||||
# |
||||
# Example: |
||||
# KEXEC_ARGS="--elf32-core-headers" |
||||
KEXEC_ARGS="" |
||||
|
||||
#Where to find the boot image |
||||
#KDUMP_BOOTDIR="/boot" |
||||
|
||||
#What is the image type used for kdump |
||||
KDUMP_IMG="vmlinuz" |
||||
|
||||
# Logging is controlled by following variables in the first kernel: |
||||
# - @var KDUMP_STDLOGLVL - logging level to standard error (console output) |
||||
# - @var KDUMP_SYSLOGLVL - logging level to syslog (by logger command) |
||||
# - @var KDUMP_KMSGLOGLVL - logging level to /dev/kmsg (only for boot-time) |
||||
# |
||||
# In the second kernel, kdump will use the rd.kdumploglvl option to set the |
||||
# log level in the above KDUMP_COMMANDLINE_APPEND. |
||||
# - @var rd.kdumploglvl - logging level to syslog (by logger command) |
||||
# - for example: add the rd.kdumploglvl=3 option to KDUMP_COMMANDLINE_APPEND |
||||
# |
||||
# Logging levels: no logging(0), error(1),warn(2),info(3),debug(4) |
||||
# |
||||
# KDUMP_STDLOGLVL=3 |
||||
# KDUMP_SYSLOGLVL=0 |
||||
# KDUMP_KMSGLOGLVL=0 |
||||
@ -0,0 +1,53 @@
@@ -0,0 +1,53 @@
|
||||
# Kernel Version string for the -kdump kernel, such as 2.6.13-1544.FC5kdump |
||||
# If no version is specified, then the init script will try to find a |
||||
# kdump kernel with the same version number as the running kernel. |
||||
KDUMP_KERNELVER="" |
||||
|
||||
# The kdump commandline is the command line that needs to be passed off to |
||||
# the kdump kernel. This will likely match the contents of the grub kernel |
||||
# line. For example: |
||||
# KDUMP_COMMANDLINE="ro root=LABEL=/" |
||||
# Dracut depends on proper root= options, so please make sure that appropriate |
||||
# root= options are copied from /proc/cmdline. In general it is best to append |
||||
# command line options using "KDUMP_COMMANDLINE_APPEND=". |
||||
# If a command line is not specified, the default will be taken from |
||||
# /proc/cmdline |
||||
KDUMP_COMMANDLINE="" |
||||
|
||||
# This variable lets us remove arguments from the current kdump commandline |
||||
# as taken from either KDUMP_COMMANDLINE above, or from /proc/cmdline |
||||
# NOTE: some arguments such as crashkernel will always be removed |
||||
KDUMP_COMMANDLINE_REMOVE="hugepages hugepagesz slub_debug quiet log_buf_len swiotlb cma hugetlb_cma" |
||||
|
||||
# This variable lets us append arguments to the current kdump commandline |
||||
# after processed by KDUMP_COMMANDLINE_REMOVE |
||||
KDUMP_COMMANDLINE_APPEND="irqpoll nr_cpus=1 reset_devices cgroup_disable=memory udev.children-max=2 panic=10 swiotlb=noforce novmcoredd cma=0 hugetlb_cma=0" |
||||
|
||||
# Any additional kexec arguments required. In most situations, this should |
||||
# be left empty |
||||
# |
||||
# Example: |
||||
# KEXEC_ARGS="--elf32-core-headers" |
||||
KEXEC_ARGS="-s" |
||||
|
||||
#Where to find the boot image |
||||
#KDUMP_BOOTDIR="/boot" |
||||
|
||||
#What is the image type used for kdump |
||||
KDUMP_IMG="vmlinuz" |
||||
|
||||
# Logging is controlled by following variables in the first kernel: |
||||
# - @var KDUMP_STDLOGLVL - logging level to standard error (console output) |
||||
# - @var KDUMP_SYSLOGLVL - logging level to syslog (by logger command) |
||||
# - @var KDUMP_KMSGLOGLVL - logging level to /dev/kmsg (only for boot-time) |
||||
# |
||||
# In the second kernel, kdump will use the rd.kdumploglvl option to set the |
||||
# log level in the above KDUMP_COMMANDLINE_APPEND. |
||||
# - @var rd.kdumploglvl - logging level to syslog (by logger command) |
||||
# - for example: add the rd.kdumploglvl=3 option to KDUMP_COMMANDLINE_APPEND |
||||
# |
||||
# Logging levels: no logging(0), error(1),warn(2),info(3),debug(4) |
||||
# |
||||
# KDUMP_STDLOGLVL=3 |
||||
# KDUMP_SYSLOGLVL=0 |
||||
# KDUMP_KMSGLOGLVL=0 |
||||
@ -0,0 +1,56 @@
@@ -0,0 +1,56 @@
|
||||
# Kernel Version string for the -kdump kernel, such as 2.6.13-1544.FC5kdump |
||||
# If no version is specified, then the init script will try to find a |
||||
# kdump kernel with the same version number as the running kernel. |
||||
KDUMP_KERNELVER="" |
||||
|
||||
# The kdump commandline is the command line that needs to be passed off to |
||||
# the kdump kernel. This will likely match the contents of the grub kernel |
||||
# line. For example: |
||||
# KDUMP_COMMANDLINE="ro root=LABEL=/" |
||||
# Dracut depends on proper root= options, so please make sure that appropriate |
||||
# root= options are copied from /proc/cmdline. In general it is best to append |
||||
# command line options using "KDUMP_COMMANDLINE_APPEND=". |
||||
# If a command line is not specified, the default will be taken from |
||||
# /proc/cmdline |
||||
KDUMP_COMMANDLINE="" |
||||
|
||||
# This variable lets us remove arguments from the current kdump commandline |
||||
# as taken from either KDUMP_COMMANDLINE above, or from /proc/cmdline |
||||
# NOTE: some arguments such as crashkernel will always be removed |
||||
KDUMP_COMMANDLINE_REMOVE="hugepages hugepagesz slub_debug quiet log_buf_len swiotlb cma hugetlb_cma" |
||||
|
||||
# This variable lets us append arguments to the current kdump commandline |
||||
# after processed by KDUMP_COMMANDLINE_REMOVE |
||||
KDUMP_COMMANDLINE_APPEND="irqpoll nr_cpus=1 reset_devices numa=off udev.children-max=2 panic=10 transparent_hugepage=never novmcoredd cma=0 hugetlb_cma=0" |
||||
|
||||
# Any additional kexec arguments required. In most situations, this should |
||||
# be left empty |
||||
# |
||||
# Example: |
||||
# KEXEC_ARGS="--elf32-core-headers" |
||||
KEXEC_ARGS="" |
||||
|
||||
#Where to find the boot image |
||||
#KDUMP_BOOTDIR="/boot" |
||||
|
||||
#What is the image type used for kdump |
||||
KDUMP_IMG="vmlinuz" |
||||
|
||||
#What is the images extension. Relocatable kernels don't have one |
||||
KDUMP_IMG_EXT="" |
||||
|
||||
# Logging is controlled by following variables in the first kernel: |
||||
# - @var KDUMP_STDLOGLVL - logging level to standard error (console output) |
||||
# - @var KDUMP_SYSLOGLVL - logging level to syslog (by logger command) |
||||
# - @var KDUMP_KMSGLOGLVL - logging level to /dev/kmsg (only for boot-time) |
||||
# |
||||
# In the second kernel, kdump will use the rd.kdumploglvl option to set the |
||||
# log level in the above KDUMP_COMMANDLINE_APPEND. |
||||
# - @var rd.kdumploglvl - logging level to syslog (by logger command) |
||||
# - for example: add the rd.kdumploglvl=3 option to KDUMP_COMMANDLINE_APPEND |
||||
# |
||||
# Logging levels: no logging(0), error(1),warn(2),info(3),debug(4) |
||||
# |
||||
# KDUMP_STDLOGLVL=3 |
||||
# KDUMP_SYSLOGLVL=0 |
||||
# KDUMP_KMSGLOGLVL=0 |
||||
@ -0,0 +1,58 @@
@@ -0,0 +1,58 @@
|
||||
# Kernel Version string for the -kdump kernel, such as 2.6.13-1544.FC5kdump |
||||
# If no version is specified, then the init script will try to find a |
||||
# kdump kernel with the same version number as the running kernel. |
||||
KDUMP_KERNELVER="" |
||||
|
||||
# The kdump commandline is the command line that needs to be passed off to |
||||
# the kdump kernel. This will likely match the contents of the grub kernel |
||||
# line. For example: |
||||
# KDUMP_COMMANDLINE="ro root=LABEL=/" |
||||
# Dracut depends on proper root= options, so please make sure that appropriate |
||||
# root= options are copied from /proc/cmdline. In general it is best to append |
||||
# command line options using "KDUMP_COMMANDLINE_APPEND=". |
||||
# If a command line is not specified, the default will be taken from |
||||
# /proc/cmdline |
||||
KDUMP_COMMANDLINE="" |
||||
|
||||
# This variable lets us remove arguments from the current kdump commandline |
||||
# as taken from either KDUMP_COMMANDLINE above, or from /proc/cmdline |
||||
# NOTE: some arguments such as crashkernel will always be removed |
||||
KDUMP_COMMANDLINE_REMOVE="hugepages hugepagesz slub_debug quiet log_buf_len swiotlb hugetlb_cma" |
||||
|
||||
# This variable lets us append arguments to the current kdump commandline |
||||
# after processed by KDUMP_COMMANDLINE_REMOVE |
||||
KDUMP_COMMANDLINE_APPEND="irqpoll maxcpus=1 noirqdistrib reset_devices cgroup_disable=memory numa=off udev.children-max=2 ehea.use_mcs=0 panic=10 kvm_cma_resv_ratio=0 transparent_hugepage=never novmcoredd hugetlb_cma=0" |
||||
|
||||
# Any additional kexec arguments required. In most situations, this should |
||||
# be left empty |
||||
# |
||||
# Example: |
||||
# KEXEC_ARGS="--elf32-core-headers" |
||||
KEXEC_ARGS="--dt-no-old-root" |
||||
|
||||
#Where to find the boot image |
||||
#KDUMP_BOOTDIR="/boot" |
||||
|
||||
#What is the image type used for kdump |
||||
KDUMP_IMG="vmlinuz" |
||||
|
||||
#What is the images extension. Relocatable kernels don't have one |
||||
KDUMP_IMG_EXT="" |
||||
|
||||
#Specify the action after failure |
||||
|
||||
# Logging is controlled by following variables in the first kernel: |
||||
# - @var KDUMP_STDLOGLVL - logging level to standard error (console output) |
||||
# - @var KDUMP_SYSLOGLVL - logging level to syslog (by logger command) |
||||
# - @var KDUMP_KMSGLOGLVL - logging level to /dev/kmsg (only for boot-time) |
||||
# |
||||
# In the second kernel, kdump will use the rd.kdumploglvl option to set the |
||||
# log level in the above KDUMP_COMMANDLINE_APPEND. |
||||
# - @var rd.kdumploglvl - logging level to syslog (by logger command) |
||||
# - for example: add the rd.kdumploglvl=3 option to KDUMP_COMMANDLINE_APPEND |
||||
# |
||||
# Logging levels: no logging(0), error(1),warn(2),info(3),debug(4) |
||||
# |
||||
# KDUMP_STDLOGLVL=3 |
||||
# KDUMP_SYSLOGLVL=0 |
||||
# KDUMP_KMSGLOGLVL=0 |
||||
@ -0,0 +1,58 @@
@@ -0,0 +1,58 @@
|
||||
# Kernel Version string for the -kdump kernel, such as 2.6.13-1544.FC5kdump |
||||
# If no version is specified, then the init script will try to find a |
||||
# kdump kernel with the same version number as the running kernel. |
||||
KDUMP_KERNELVER="" |
||||
|
||||
# The kdump commandline is the command line that needs to be passed off to |
||||
# the kdump kernel. This will likely match the contents of the grub kernel |
||||
# line. For example: |
||||
# KDUMP_COMMANDLINE="ro root=LABEL=/" |
||||
# Dracut depends on proper root= options, so please make sure that appropriate |
||||
# root= options are copied from /proc/cmdline. In general it is best to append |
||||
# command line options using "KDUMP_COMMANDLINE_APPEND=". |
||||
# If a command line is not specified, the default will be taken from |
||||
# /proc/cmdline |
||||
KDUMP_COMMANDLINE="" |
||||
|
||||
# This variable lets us remove arguments from the current kdump commandline |
||||
# as taken from either KDUMP_COMMANDLINE above, or from /proc/cmdline |
||||
# NOTE: some arguments such as crashkernel will always be removed |
||||
KDUMP_COMMANDLINE_REMOVE="hugepages hugepagesz slub_debug quiet log_buf_len swiotlb hugetlb_cma" |
||||
|
||||
# This variable lets us append arguments to the current kdump commandline |
||||
# after processed by KDUMP_COMMANDLINE_REMOVE |
||||
KDUMP_COMMANDLINE_APPEND="irqpoll maxcpus=1 noirqdistrib reset_devices cgroup_disable=memory numa=off udev.children-max=2 ehea.use_mcs=0 panic=10 kvm_cma_resv_ratio=0 transparent_hugepage=never novmcoredd hugetlb_cma=0" |
||||
|
||||
# Any additional kexec arguments required. In most situations, this should |
||||
# be left empty |
||||
# |
||||
# Example: |
||||
# KEXEC_ARGS="--elf32-core-headers" |
||||
KEXEC_ARGS="--dt-no-old-root -s" |
||||
|
||||
#Where to find the boot image |
||||
#KDUMP_BOOTDIR="/boot" |
||||
|
||||
#What is the image type used for kdump |
||||
KDUMP_IMG="vmlinuz" |
||||
|
||||
#What is the images extension. Relocatable kernels don't have one |
||||
KDUMP_IMG_EXT="" |
||||
|
||||
#Specify the action after failure |
||||
|
||||
# Logging is controlled by following variables in the first kernel: |
||||
# - @var KDUMP_STDLOGLVL - logging level to standard error (console output) |
||||
# - @var KDUMP_SYSLOGLVL - logging level to syslog (by logger command) |
||||
# - @var KDUMP_KMSGLOGLVL - logging level to /dev/kmsg (only for boot-time) |
||||
# |
||||
# In the second kernel, kdump will use the rd.kdumploglvl option to set the |
||||
# log level in the above KDUMP_COMMANDLINE_APPEND. |
||||
# - @var rd.kdumploglvl - logging level to syslog (by logger command) |
||||
# - for example: add the rd.kdumploglvl=3 option to KDUMP_COMMANDLINE_APPEND |
||||
# |
||||
# Logging levels: no logging(0), error(1),warn(2),info(3),debug(4) |
||||
# |
||||
# KDUMP_STDLOGLVL=3 |
||||
# KDUMP_SYSLOGLVL=0 |
||||
# KDUMP_KMSGLOGLVL=0 |
||||
@ -0,0 +1,59 @@
@@ -0,0 +1,59 @@
|
||||
# Kernel Version string for the -kdump kernel, such as 2.6.13-1544.FC5kdump |
||||
# If no version is specified, then the init script will try to find a |
||||
# kdump kernel with the same version number as the running kernel. |
||||
KDUMP_KERNELVER="" |
||||
|
||||
# The kdump commandline is the command line that needs to be passed off to |
||||
# the kdump kernel. This will likely match the contents of the grub kernel |
||||
# line. For example: |
||||
# KDUMP_COMMANDLINE="ro root=LABEL=/" |
||||
# Dracut depends on proper root= options, so please make sure that appropriate |
||||
# root= options are copied from /proc/cmdline. In general it is best to append |
||||
# command line options using "KDUMP_COMMANDLINE_APPEND=". |
||||
# If a command line is not specified, the default will be taken from |
||||
# /proc/cmdline |
||||
KDUMP_COMMANDLINE="" |
||||
|
||||
# This variable lets us remove arguments from the current kdump commandline |
||||
# as taken from either KDUMP_COMMANDLINE above, or from /proc/cmdline |
||||
# NOTE: some arguments such as crashkernel will always be removed |
||||
KDUMP_COMMANDLINE_REMOVE="hugepages hugepagesz slub_debug quiet log_buf_len swiotlb vmcp_cma cma hugetlb_cma prot_virt" |
||||
|
||||
# This variable lets us append arguments to the current kdump commandline |
||||
# after processed by KDUMP_COMMANDLINE_REMOVE |
||||
KDUMP_COMMANDLINE_APPEND="nr_cpus=1 cgroup_disable=memory numa=off udev.children-max=2 panic=10 transparent_hugepage=never novmcoredd vmcp_cma=0 cma=0 hugetlb_cma=0" |
||||
|
||||
# Any additional /sbin/mkdumprd arguments required. |
||||
MKDUMPRD_ARGS="" |
||||
|
||||
# Any additional kexec arguments required. In most situations, this should |
||||
# be left empty |
||||
# |
||||
# Example: |
||||
# KEXEC_ARGS="--elf32-core-headers" |
||||
KEXEC_ARGS="-s" |
||||
|
||||
#Where to find the boot image |
||||
#KDUMP_BOOTDIR="/boot" |
||||
|
||||
#What is the image type used for kdump |
||||
KDUMP_IMG="vmlinuz" |
||||
|
||||
#What is the images extension. Relocatable kernels don't have one |
||||
KDUMP_IMG_EXT="" |
||||
|
||||
# Logging is controlled by following variables in the first kernel: |
||||
# - @var KDUMP_STDLOGLVL - logging level to standard error (console output) |
||||
# - @var KDUMP_SYSLOGLVL - logging level to syslog (by logger command) |
||||
# - @var KDUMP_KMSGLOGLVL - logging level to /dev/kmsg (only for boot-time) |
||||
# |
||||
# In the second kernel, kdump will use the rd.kdumploglvl option to set the |
||||
# log level in the above KDUMP_COMMANDLINE_APPEND. |
||||
# - @var rd.kdumploglvl - logging level to syslog (by logger command) |
||||
# - for example: add the rd.kdumploglvl=3 option to KDUMP_COMMANDLINE_APPEND |
||||
# |
||||
# Logging levels: no logging(0), error(1),warn(2),info(3),debug(4) |
||||
# |
||||
# KDUMP_STDLOGLVL=3 |
||||
# KDUMP_SYSLOGLVL=0 |
||||
# KDUMP_KMSGLOGLVL=0 |
||||
@ -0,0 +1,56 @@
@@ -0,0 +1,56 @@
|
||||
# Kernel Version string for the -kdump kernel, such as 2.6.13-1544.FC5kdump |
||||
# If no version is specified, then the init script will try to find a |
||||
# kdump kernel with the same version number as the running kernel. |
||||
KDUMP_KERNELVER="" |
||||
|
||||
# The kdump commandline is the command line that needs to be passed off to |
||||
# the kdump kernel. This will likely match the contents of the grub kernel |
||||
# line. For example: |
||||
# KDUMP_COMMANDLINE="ro root=LABEL=/" |
||||
# Dracut depends on proper root= options, so please make sure that appropriate |
||||
# root= options are copied from /proc/cmdline. In general it is best to append |
||||
# command line options using "KDUMP_COMMANDLINE_APPEND=". |
||||
# If a command line is not specified, the default will be taken from |
||||
# /proc/cmdline |
||||
KDUMP_COMMANDLINE="" |
||||
|
||||
# This variable lets us remove arguments from the current kdump commandline |
||||
# as taken from either KDUMP_COMMANDLINE above, or from /proc/cmdline |
||||
# NOTE: some arguments such as crashkernel will always be removed |
||||
KDUMP_COMMANDLINE_REMOVE="hugepages hugepagesz slub_debug quiet log_buf_len swiotlb cma hugetlb_cma" |
||||
|
||||
# This variable lets us append arguments to the current kdump commandline |
||||
# after processed by KDUMP_COMMANDLINE_REMOVE |
||||
KDUMP_COMMANDLINE_APPEND="irqpoll nr_cpus=1 reset_devices cgroup_disable=memory mce=off numa=off udev.children-max=2 panic=10 acpi_no_memhotplug transparent_hugepage=never nokaslr hest_disable novmcoredd cma=0 hugetlb_cma=0" |
||||
|
||||
# Any additional kexec arguments required. In most situations, this should |
||||
# be left empty |
||||
# |
||||
# Example: |
||||
# KEXEC_ARGS="--elf32-core-headers" |
||||
KEXEC_ARGS="-s" |
||||
|
||||
#Where to find the boot image |
||||
#KDUMP_BOOTDIR="/boot" |
||||
|
||||
#What is the image type used for kdump |
||||
KDUMP_IMG="vmlinuz" |
||||
|
||||
#What is the images extension. Relocatable kernels don't have one |
||||
KDUMP_IMG_EXT="" |
||||
|
||||
# Logging is controlled by following variables in the first kernel: |
||||
# - @var KDUMP_STDLOGLVL - logging level to standard error (console output) |
||||
# - @var KDUMP_SYSLOGLVL - logging level to syslog (by logger command) |
||||
# - @var KDUMP_KMSGLOGLVL - logging level to /dev/kmsg (only for boot-time) |
||||
# |
||||
# In the second kernel, kdump will use the rd.kdumploglvl option to set the |
||||
# log level in the above KDUMP_COMMANDLINE_APPEND. |
||||
# - @var rd.kdumploglvl - logging level to syslog (by logger command) |
||||
# - for example: add the rd.kdumploglvl=3 option to KDUMP_COMMANDLINE_APPEND |
||||
# |
||||
# Logging levels: no logging(0), error(1),warn(2),info(3),debug(4) |
||||
# |
||||
# KDUMP_STDLOGLVL=3 |
||||
# KDUMP_SYSLOGLVL=0 |
||||
# KDUMP_KMSGLOGLVL=0 |
||||
@ -0,0 +1,69 @@
@@ -0,0 +1,69 @@
|
||||
.TH KDUMPCTL 8 2015-07-13 kexec-tools |
||||
|
||||
.SH NAME |
||||
kdumpctl \- control interface for kdump |
||||
|
||||
.SH SYNOPSIS |
||||
.B kdumpctl |
||||
.I COMMAND |
||||
|
||||
.SH DESCRIPTION |
||||
.B kdumpctl |
||||
is used to check or control the kdump service. |
||||
In most cases, you should use |
||||
.B systemctl |
||||
to start / stop / enable kdump service instead. However, |
||||
.B kdumpctl |
||||
provides more details for debug and a helper to setup ssh key authentication. |
||||
|
||||
.SH COMMANDS |
||||
.TP |
||||
.I start |
||||
Start the service. |
||||
.TP |
||||
.I stop |
||||
Stop the service. |
||||
.TP |
||||
.I status |
||||
Prints the current status of kdump service. |
||||
It returns non-zero value if kdump is not operational. |
||||
.TP |
||||
.I restart |
||||
Is equal to |
||||
.I start; stop |
||||
.TP |
||||
.I reload |
||||
reload crash kernel image and initramfs without triggering a rebuild. |
||||
.TP |
||||
.I rebuild |
||||
rebuild the crash kernel initramfs. |
||||
.TP |
||||
.I propagate |
||||
Helps to setup key authentication for ssh storage since it's |
||||
impossible to use password authentication during kdump. |
||||
.TP |
||||
.I showmem |
||||
Prints the size of reserved memory for crash kernel in megabytes. |
||||
.TP |
||||
.I estimate |
||||
Estimate a suitable crashkernel value for current machine. This is a |
||||
best-effort estimate. It will print a recommanded crashkernel value |
||||
based on current kdump setup, and list some details of memory usage. |
||||
.TP |
||||
.I reset-crashkernel [--kernel=path_to_kernel] [--reboot] |
||||
Reset crashkernel to default value recommended by kexec-tools. If no kernel |
||||
is specified, will reset KDUMP_KERNELVER if it's defined in /etc/sysconfig/kdump |
||||
or current running kernel's crashkernel value if KDUMP_KERNELVER is empty. You can |
||||
also specify --kernel=ALL and --kernel=DEFAULT which have the same meaning as |
||||
grubby's kernel-path=ALL and kernel-path=DEFAULT. ppc64le supports FADump and |
||||
supports an additonal [--fadump=[on|off|nocma]] parameter to toggle FADump |
||||
on/off. |
||||
|
||||
Note: The memory requirements for kdump varies heavily depending on the |
||||
used hardware and system configuration. Thus the recommended |
||||
crashkernel might not work for your specific setup. Please test if |
||||
kdump works after resetting the crashkernel value. |
||||
|
||||
.SH "SEE ALSO" |
||||
.BR kdump.conf (5), |
||||
.BR mkdumprd (8) |
||||
@ -0,0 +1,95 @@
@@ -0,0 +1,95 @@
|
||||
commit 186e7b0752d8fce1618fa37519671c834c46340e |
||||
Author: Alexander Egorenkov <egorenar@linux.ibm.com> |
||||
Date: Wed Dec 15 18:48:53 2021 +0100 |
||||
|
||||
s390: handle R_390_PLT32DBL reloc entries in machine_apply_elf_rel() |
||||
|
||||
Starting with gcc 11.3, the C compiler will generate PLT-relative function |
||||
calls even if they are local and do not require it. Later on during linking, |
||||
the linker will replace all PLT-relative calls to local functions with |
||||
PC-relative ones. Unfortunately, the purgatory code of kexec/kdump is |
||||
not being linked as a regular executable or shared library would have been, |
||||
and therefore, all PLT-relative addresses remain in the generated purgatory |
||||
object code unresolved. This in turn lets kexec-tools fail with |
||||
"Unknown rela relocation: 0x14 0x73c0901c" for such relocation types. |
||||
|
||||
Furthermore, the clang C compiler has always behaved like described above |
||||
and this commit should fix the purgatory code built with the latter. |
||||
|
||||
Because the purgatory code is no regular executable or shared library, |
||||
contains only calls to local functions and has no PLT, all R_390_PLT32DBL |
||||
relocation entries can be resolved just like a R_390_PC32DBL one. |
||||
|
||||
* https://refspecs.linuxfoundation.org/ELF/zSeries/lzsabi0_zSeries/x1633.html#AEN1699 |
||||
|
||||
Relocation entries of purgatory code generated with gcc 11.3 |
||||
------------------------------------------------------------ |
||||
|
||||
$ readelf -r purgatory/purgatory.o |
||||
|
||||
Relocation section '.rela.text' at offset 0x6e8 contains 27 entries: |
||||
Offset Info Type Sym. Value Sym. Name + Addend |
||||
00000000000c 000300000013 R_390_PC32DBL 0000000000000000 .data + 2 |
||||
00000000001a 001000000014 R_390_PLT32DBL 0000000000000000 sha256_starts + 2 |
||||
000000000030 001100000014 R_390_PLT32DBL 0000000000000000 sha256_update + 2 |
||||
000000000046 001200000014 R_390_PLT32DBL 0000000000000000 sha256_finish + 2 |
||||
000000000050 000300000013 R_390_PC32DBL 0000000000000000 .data + 102 |
||||
00000000005a 001300000014 R_390_PLT32DBL 0000000000000000 memcmp + 2 |
||||
... |
||||
000000000118 001600000014 R_390_PLT32DBL 0000000000000000 setup_arch + 2 |
||||
00000000011e 000300000013 R_390_PC32DBL 0000000000000000 .data + 2 |
||||
00000000012c 000f00000014 R_390_PLT32DBL 0000000000000000 verify_sha256_digest + 2 |
||||
000000000142 001700000014 R_390_PLT32DBL 0000000000000000 |
||||
post_verification[...] + 2 |
||||
|
||||
Relocation entries of purgatory code generated with gcc 11.2 |
||||
------------------------------------------------------------ |
||||
|
||||
$ readelf -r purgatory/purgatory.o |
||||
|
||||
Relocation section '.rela.text' at offset 0x6e8 contains 27 entries: |
||||
Offset Info Type Sym. Value Sym. Name + Addend |
||||
00000000000e 000300000013 R_390_PC32DBL 0000000000000000 .data + 2 |
||||
00000000001c 001000000013 R_390_PC32DBL 0000000000000000 sha256_starts + 2 |
||||
000000000036 001100000013 R_390_PC32DBL 0000000000000000 sha256_update + 2 |
||||
000000000048 001200000013 R_390_PC32DBL 0000000000000000 sha256_finish + 2 |
||||
000000000052 000300000013 R_390_PC32DBL 0000000000000000 .data + 102 |
||||
00000000005c 001300000013 R_390_PC32DBL 0000000000000000 memcmp + 2 |
||||
... |
||||
00000000011a 001600000013 R_390_PC32DBL 0000000000000000 setup_arch + 2 |
||||
000000000120 000300000013 R_390_PC32DBL 0000000000000000 .data + 122 |
||||
000000000130 000f00000013 R_390_PC32DBL 0000000000000000 verify_sha256_digest + 2 |
||||
000000000146 001700000013 R_390_PC32DBL 0000000000000000 post_verification[...] + 2 |
||||
|
||||
Corresponding s390 kernel discussion: |
||||
* https://lore.kernel.org/linux-s390/20211208105801.188140-1-egorenar@linux.ibm.com/T/#u |
||||
|
||||
Signed-off-by: Alexander Egorenkov <egorenar@linux.ibm.com> |
||||
Reported-by: Tao Liu <ltao@redhat.com> |
||||
Suggested-by: Philipp Rudo <prudo@redhat.com> |
||||
Reviewed-by: Philipp Rudo <prudo@redhat.com> |
||||
[hca@linux.ibm.com: changed commit message as requested by Philipp Rudo] |
||||
Signed-off-by: Heiko Carstens <hca@linux.ibm.com> |
||||
Signed-off-by: Simon Horman <horms@verge.net.au> |
||||
|
||||
diff --git a/kexec/arch/s390/kexec-elf-rel-s390.c b/kexec/arch/s390/kexec-elf-rel-s390.c |
||||
index a5e1b73455785ae3bc3aa72b3beee13ae202e82f..91ba86a9991dad4271b834fc3b24861c40309e52 100644 |
||||
--- a/kexec/arch/s390/kexec-elf-rel-s390.c |
||||
+++ b/kexec/arch/s390/kexec-elf-rel-s390.c |
||||
@@ -56,6 +56,7 @@ void machine_apply_elf_rel(struct mem_ehdr *UNUSED(ehdr), |
||||
case R_390_PC16: /* PC relative 16 bit. */ |
||||
case R_390_PC16DBL: /* PC relative 16 bit shifted by 1. */ |
||||
case R_390_PC32DBL: /* PC relative 32 bit shifted by 1. */ |
||||
+ case R_390_PLT32DBL: /* 32 bit PC rel. PLT shifted by 1. */ |
||||
case R_390_PC32: /* PC relative 32 bit. */ |
||||
case R_390_PC64: /* PC relative 64 bit. */ |
||||
val -= address; |
||||
@@ -63,7 +64,7 @@ void machine_apply_elf_rel(struct mem_ehdr *UNUSED(ehdr), |
||||
*(unsigned short *) loc = val; |
||||
else if (r_type == R_390_PC16DBL) |
||||
*(unsigned short *) loc = val >> 1; |
||||
- else if (r_type == R_390_PC32DBL) |
||||
+ else if (r_type == R_390_PC32DBL || r_type == R_390_PLT32DBL) |
||||
*(unsigned int *) loc = val >> 1; |
||||
else if (r_type == R_390_PC32) |
||||
*(unsigned int *) loc = val; |
||||
@ -0,0 +1,49 @@
@@ -0,0 +1,49 @@
|
||||
From 59b1726fbcc251155140c8a1972384498fee4daf Mon Sep 17 00:00:00 2001 |
||||
From: HATAYAMA Daisuke <d.hatayama@fujitsu.com> |
||||
Date: Tue, 25 Jan 2022 12:55:15 +0000 |
||||
Subject: [PATCH] [PATCH] sadump, kaslr: fix failure of calculating |
||||
kaslr_offset |
||||
|
||||
On kernels v5.8 or later, makedumpfile fails for memory dumps in the |
||||
sadump-related formats as follows: |
||||
|
||||
# makedumpfile -f -l -d 31 -x ./vmlinux /dev/sdd4 /root/vmcore-ld31 |
||||
__vtop4_x86_64: Can't get a valid pud_pte. |
||||
...110 lines of the same message... |
||||
__vtop4_x86_64: Can't get a valid pud_pte. |
||||
calc_kaslr_offset: failed to calculate kaslr_offset and phys_base; default to 0 |
||||
readmem: type_addr: 1, addr:ffffffff85411858, size:8 |
||||
__vtop4_x86_64: Can't get pgd (page_dir:ffffffff85411858). |
||||
readmem: Can't convert a virtual address(ffffffff059be980) to physical address. |
||||
readmem: type_addr: 0, addr:ffffffff059be980, size:1024 |
||||
cpu_online_mask_init: Can't read cpu_online_mask memory. |
||||
|
||||
makedumpfile Failed. |
||||
|
||||
This is caused by the kernel commit 9d06c4027f21 ("x86/entry: Convert |
||||
Divide Error to IDTENTRY") that renamed divide_error to |
||||
asm_exc_divide_error, breaking logic for calculating kaslr offset. |
||||
|
||||
Fix this by adding initialization of asm_exc_divide_error. |
||||
|
||||
Signed-off-by: HATAYAMA Daisuke <d.hatayama@fujitsu.com> |
||||
--- |
||||
makedumpfile.c | 2 ++ |
||||
1 file changed, 2 insertions(+) |
||||
|
||||
diff --git a/makedumpfile-1.7.0/makedumpfile.c b/makedumpfile-1.7.0/makedumpfile.c |
||||
index a51bdaf..7ed9756 100644 |
||||
--- a/makedumpfile-1.7.0/makedumpfile.c |
||||
+++ b/makedumpfile-1.7.0/makedumpfile.c |
||||
@@ -1667,6 +1667,8 @@ get_symbol_info(void) |
||||
SYMBOL_INIT(cur_cpu_spec, "cur_cpu_spec"); |
||||
|
||||
SYMBOL_INIT(divide_error, "divide_error"); |
||||
+ if (SYMBOL(divide_error) == NOT_FOUND_SYMBOL) |
||||
+ SYMBOL_INIT(divide_error, "asm_exc_divide_error"); |
||||
SYMBOL_INIT(idt_table, "idt_table"); |
||||
SYMBOL_INIT(saved_command_line, "saved_command_line"); |
||||
SYMBOL_INIT(pti_init, "pti_init"); |
||||
-- |
||||
2.33.1 |
||||
|
||||
@ -0,0 +1,25 @@
@@ -0,0 +1,25 @@
|
||||
Kdump now works on live images with some manual configurations. Here is the step |
||||
by step guide. |
||||
|
||||
1. Enable crashkernel reservation |
||||
|
||||
Since there isn't any config file that can be used to configure kernel |
||||
parameters for live images before booting them, we have to append 'crashkernel' |
||||
argument in boot menu every time we boot a live image. |
||||
|
||||
2. Change dump target in /etc/kdump.conf |
||||
|
||||
When kdump kernel boots in a live environment, the default target /var/crash is |
||||
in RAM so you need to change the dump target to an external disk or a network |
||||
dump target. |
||||
|
||||
Besides, make sure that "default dump_to_rootfs" is not specified. |
||||
|
||||
3. Start kdump service |
||||
|
||||
$ kdumpctl start |
||||
|
||||
4. Trigger a kdump test |
||||
|
||||
$ echo 1 > /proc/sys/kernel/sysrq |
||||
$ echo c > /proc/sysrq-trigger |
||||
@ -0,0 +1,469 @@
@@ -0,0 +1,469 @@
|
||||
#!/bin/bash --norc |
||||
# New mkdumprd |
||||
# |
||||
# Copyright 2011 Red Hat, Inc. |
||||
# |
||||
# Written by Cong Wang <amwang@redhat.com> |
||||
# |
||||
|
||||
if [[ -f /etc/sysconfig/kdump ]]; then |
||||
. /etc/sysconfig/kdump |
||||
fi |
||||
|
||||
[[ $dracutbasedir ]] || dracutbasedir=/usr/lib/dracut |
||||
. $dracutbasedir/dracut-functions.sh |
||||
. /lib/kdump/kdump-lib.sh |
||||
. /lib/kdump/kdump-logger.sh |
||||
export IN_KDUMP=1 |
||||
|
||||
#initiate the kdump logger |
||||
if ! dlog_init; then |
||||
echo "failed to initiate the kdump logger." |
||||
exit 1 |
||||
fi |
||||
|
||||
SSH_KEY_LOCATION="/root/.ssh/kdump_id_rsa" |
||||
SAVE_PATH=$(get_save_path) |
||||
OVERRIDE_RESETTABLE=0 |
||||
|
||||
extra_modules="" |
||||
dracut_args=(--add kdumpbase --quiet --hostonly --hostonly-cmdline --hostonly-i18n --hostonly-mode strict -o "plymouth resume ifcfg earlykdump") |
||||
|
||||
MKDUMPRD_TMPDIR="$(mktemp -d -t mkdumprd.XXXXXX)" |
||||
[ -d "$MKDUMPRD_TMPDIR" ] || perror_exit "dracut: mktemp -p -d -t dracut.XXXXXX failed." |
||||
MKDUMPRD_TMPMNT="$MKDUMPRD_TMPDIR/target" |
||||
|
||||
trap ' |
||||
ret=$?; |
||||
is_mounted $MKDUMPRD_TMPMNT && umount -f $MKDUMPRD_TMPMNT; |
||||
[[ -d $MKDUMPRD_TMPDIR ]] && rm --one-file-system -rf -- "$MKDUMPRD_TMPDIR"; |
||||
exit $ret; |
||||
' EXIT |
||||
|
||||
# clean up after ourselves no matter how we die. |
||||
trap 'exit 1;' SIGINT |
||||
|
||||
add_dracut_arg() |
||||
{ |
||||
dracut_args+=("$@") |
||||
} |
||||
|
||||
add_dracut_mount() |
||||
{ |
||||
add_dracut_arg "--mount" "$1" |
||||
} |
||||
|
||||
add_dracut_sshkey() |
||||
{ |
||||
add_dracut_arg "--sshkey" "$1" |
||||
} |
||||
|
||||
# caller should ensure $1 is valid and mounted in 1st kernel |
||||
to_mount() |
||||
{ |
||||
local _target=$1 _fstype=$2 _options=$3 _sed_cmd _new_mntpoint _pdev |
||||
|
||||
_new_mntpoint=$(get_kdump_mntpoint_from_target "$_target") |
||||
_fstype="${_fstype:-$(get_fs_type_from_target "$_target")}" |
||||
_options="${_options:-$(get_mntopt_from_target "$_target")}" |
||||
_options="${_options:-defaults}" |
||||
|
||||
if [[ $_fstype == "nfs"* ]]; then |
||||
_pdev=$_target |
||||
_sed_cmd+='s/,\(mount\)\?addr=[^,]*//g;' |
||||
_sed_cmd+='s/,\(mount\)\?proto=[^,]*//g;' |
||||
_sed_cmd+='s/,clientaddr=[^,]*//;' |
||||
else |
||||
# for non-nfs _target converting to use udev persistent name |
||||
_pdev="$(kdump_get_persistent_dev "$_target")" |
||||
if [[ -z $_pdev ]]; then |
||||
return 1 |
||||
fi |
||||
fi |
||||
|
||||
# mount fs target as rw in 2nd kernel |
||||
_sed_cmd+='s/\(^\|,\)ro\($\|,\)/\1rw\2/g;' |
||||
# with 'noauto' in fstab nfs and non-root disk mount will fail in 2nd |
||||
# kernel, filter it out here. |
||||
_sed_cmd+='s/\(^\|,\)noauto\($\|,\)/\1/g;' |
||||
# drop nofail or nobootwait |
||||
_sed_cmd+='s/\(^\|,\)nofail\($\|,\)/\1/g;' |
||||
_sed_cmd+='s/\(^\|,\)nobootwait\($\|,\)/\1/g;' |
||||
|
||||
_options=$(echo "$_options" | sed "$_sed_cmd") |
||||
|
||||
echo "$_pdev $_new_mntpoint $_fstype $_options" |
||||
} |
||||
|
||||
#Function: get_ssh_size |
||||
#$1=dump target |
||||
#called from while loop and shouldn't read from stdin, so we're using "ssh -n" |
||||
get_ssh_size() |
||||
{ |
||||
local _out |
||||
local _opt=("-i" "$SSH_KEY_LOCATION" "-o" "BatchMode=yes" "-o" "StrictHostKeyChecking=yes") |
||||
|
||||
if ! _out=$(ssh -q -n "${_opt[@]}" "$1" "df" "--output=avail" "$SAVE_PATH"); then |
||||
perror_exit "checking remote ssh server available size failed." |
||||
fi |
||||
|
||||
echo -n "$_out" | tail -1 |
||||
} |
||||
|
||||
#mkdir if save path does not exist on ssh dump target |
||||
#$1=ssh dump target |
||||
#caller should ensure write permission on $1:$SAVE_PATH |
||||
#called from while loop and shouldn't read from stdin, so we're using "ssh -n" |
||||
mkdir_save_path_ssh() |
||||
{ |
||||
local _opt _dir |
||||
_opt=(-i "$SSH_KEY_LOCATION" -o BatchMode=yes -o StrictHostKeyChecking=yes) |
||||
ssh -qn "${_opt[@]}" "$1" mkdir -p "$SAVE_PATH" &> /dev/null || |
||||
perror_exit "mkdir failed on $1:$SAVE_PATH" |
||||
|
||||
# check whether user has write permission on $1:$SAVE_PATH |
||||
_dir=$(ssh -qn "${_opt[@]}" "$1" mktemp -dqp "$SAVE_PATH" 2> /dev/null) || |
||||
perror_exit "Could not create temporary directory on $1:$SAVE_PATH. Make sure user has write permission on destination" |
||||
ssh -qn "${_opt[@]}" "$1" rmdir "$_dir" |
||||
|
||||
return 0 |
||||
} |
||||
|
||||
#Function: get_fs_size |
||||
#$1=dump target |
||||
get_fs_size() |
||||
{ |
||||
df --output=avail "$(get_mntpoint_from_target "$1")/$SAVE_PATH" | tail -1 |
||||
} |
||||
|
||||
#Function: get_raw_size |
||||
#$1=dump target |
||||
get_raw_size() |
||||
{ |
||||
fdisk -s "$1" |
||||
} |
||||
|
||||
#Function: check_size |
||||
#$1: dump type string ('raw', 'fs', 'ssh') |
||||
#$2: dump target |
||||
check_size() |
||||
{ |
||||
local avail memtotal |
||||
|
||||
memtotal=$(awk '/MemTotal/{print $2}' /proc/meminfo) |
||||
case "$1" in |
||||
raw) |
||||
avail=$(get_raw_size "$2") |
||||
;; |
||||
ssh) |
||||
avail=$(get_ssh_size "$2") |
||||
;; |
||||
fs) |
||||
avail=$(get_fs_size "$2") |
||||
;; |
||||
*) |
||||
return |
||||
;; |
||||
esac || perror_exit "Check dump target size failed" |
||||
|
||||
if [[ $avail -lt $memtotal ]]; then |
||||
dwarn "Warning: There might not be enough space to save a vmcore." |
||||
dwarn " The size of $2 should be greater than $memtotal kilo bytes." |
||||
fi |
||||
} |
||||
|
||||
check_save_path_fs() |
||||
{ |
||||
local _path=$1 |
||||
|
||||
if [[ ! -d $_path ]]; then |
||||
perror_exit "Dump path $_path does not exist." |
||||
fi |
||||
} |
||||
|
||||
mount_failure() |
||||
{ |
||||
local _target=$1 |
||||
local _mnt=$2 |
||||
local _fstype=$3 |
||||
local msg="Failed to mount $_target" |
||||
|
||||
if [[ -n $_mnt ]]; then |
||||
msg="$msg on $_mnt" |
||||
fi |
||||
|
||||
msg="$msg for kdump preflight check." |
||||
|
||||
if [[ $_fstype == "nfs" ]]; then |
||||
msg="$msg Please make sure nfs-utils has been installed." |
||||
fi |
||||
|
||||
perror_exit "$msg" |
||||
} |
||||
|
||||
check_user_configured_target() |
||||
{ |
||||
local _target=$1 _cfg_fs_type=$2 _mounted |
||||
local _mnt _opt _fstype |
||||
|
||||
_mnt=$(get_mntpoint_from_target "$_target") |
||||
_opt=$(get_mntopt_from_target "$_target") |
||||
_fstype=$(get_fs_type_from_target "$_target") |
||||
|
||||
if [[ -n $_fstype ]]; then |
||||
# In case of nfs4, nfs should be used instead, nfs* options is deprecated in kdump.conf |
||||
[[ $_fstype == "nfs"* ]] && _fstype=nfs |
||||
|
||||
if [[ -n $_cfg_fs_type ]] && [[ $_fstype != "$_cfg_fs_type" ]]; then |
||||
perror_exit "\"$_target\" have a wrong type config \"$_cfg_fs_type\", expected \"$_fstype\"" |
||||
fi |
||||
else |
||||
_fstype="$_cfg_fs_type" |
||||
_fstype="$_cfg_fs_type" |
||||
fi |
||||
|
||||
# For noauto mount, mount it inplace with default value. |
||||
# Else use the temporary target directory |
||||
if [[ -n $_mnt ]]; then |
||||
if ! is_mounted "$_mnt"; then |
||||
if [[ $_opt == *",noauto"* ]]; then |
||||
mount "$_mnt" || mount_failure "$_target" "$_mnt" "$_fstype" |
||||
_mounted=$_mnt |
||||
else |
||||
perror_exit "Dump target \"$_target\" is neither mounted nor configured as \"noauto\"" |
||||
fi |
||||
fi |
||||
else |
||||
_mnt=$MKDUMPRD_TMPMNT |
||||
mkdir -p "$_mnt" |
||||
mount "$_target" "$_mnt" -t "$_fstype" -o defaults || mount_failure "$_target" "" "$_fstype" |
||||
_mounted=$_mnt |
||||
fi |
||||
|
||||
# For user configured target, use $SAVE_PATH as the dump path within the target |
||||
if [[ ! -d "$_mnt/$SAVE_PATH" ]]; then |
||||
perror_exit "Dump path \"$_mnt/$SAVE_PATH\" does not exist in dump target \"$_target\"" |
||||
fi |
||||
|
||||
check_size fs "$_target" |
||||
|
||||
# Unmount it early, if function is interrupted and didn't reach here, the shell trap will clear it up anyway |
||||
if [[ -n $_mounted ]]; then |
||||
umount -f -- "$_mounted" |
||||
fi |
||||
} |
||||
|
||||
# $1: core_collector config value |
||||
verify_core_collector() |
||||
{ |
||||
local _cmd="${1%% *}" |
||||
local _params="${1#* }" |
||||
|
||||
if [[ $_cmd != "makedumpfile" ]]; then |
||||
if is_raw_dump_target; then |
||||
dwarn "Warning: specifying a non-makedumpfile core collector, you will have to recover the vmcore manually." |
||||
fi |
||||
return |
||||
fi |
||||
|
||||
if is_ssh_dump_target || is_raw_dump_target; then |
||||
if ! strstr "$_params" "-F"; then |
||||
perror_exit 'The specified dump target needs makedumpfile "-F" option.' |
||||
fi |
||||
_params="$_params vmcore" |
||||
else |
||||
_params="$_params vmcore dumpfile" |
||||
fi |
||||
|
||||
# shellcheck disable=SC2086 |
||||
if ! $_cmd --check-params $_params; then |
||||
perror_exit "makedumpfile parameter check failed." |
||||
fi |
||||
} |
||||
|
||||
add_mount() |
||||
{ |
||||
local _mnt |
||||
|
||||
_mnt=$(to_mount "$@") || exit 1 |
||||
|
||||
add_dracut_mount "$_mnt" |
||||
} |
||||
|
||||
#handle the case user does not specify the dump target explicitly |
||||
handle_default_dump_target() |
||||
{ |
||||
local _target |
||||
local _mntpoint |
||||
|
||||
is_user_configured_dump_target && return |
||||
|
||||
check_save_path_fs "$SAVE_PATH" |
||||
|
||||
_save_path=$(get_bind_mount_source "$SAVE_PATH") |
||||
_target=$(get_target_from_path "$_save_path") |
||||
_mntpoint=$(get_mntpoint_from_target "$_target") |
||||
|
||||
SAVE_PATH=${_save_path##"$_mntpoint"} |
||||
add_mount "$_target" |
||||
check_size fs "$_target" |
||||
} |
||||
|
||||
# $1: function name |
||||
for_each_block_target() |
||||
{ |
||||
local dev majmin |
||||
|
||||
for dev in $(get_kdump_targets); do |
||||
[[ -b $dev ]] || continue |
||||
majmin=$(get_maj_min "$dev") |
||||
check_block_and_slaves "$1" "$majmin" && return 1 |
||||
done |
||||
|
||||
return 0 |
||||
} |
||||
|
||||
#judge if a specific device with $1 is unresettable |
||||
#return false if unresettable. |
||||
is_unresettable() |
||||
{ |
||||
local path device resettable=1 |
||||
|
||||
path="/sys/$(udevadm info --query=all --path="/sys/dev/block/$1" | awk '/^P:/ {print $2}' | sed -e 's/\(cciss[0-9]\+\/\).*/\1/g' -e 's/\/block\/.*$//')/resettable" |
||||
if [[ -f $path ]]; then |
||||
resettable="$(< "$path")" |
||||
[[ $resettable -eq 0 ]] && [[ $OVERRIDE_RESETTABLE -eq 0 ]] && { |
||||
device=$(udevadm info --query=all --path="/sys/dev/block/$1" | awk -F= '/DEVNAME/{print $2}') |
||||
derror "Error: Can not save vmcore because device $device is unresettable" |
||||
return 0 |
||||
} |
||||
fi |
||||
|
||||
return 1 |
||||
} |
||||
|
||||
#check if machine is resettable. |
||||
#return true if resettable |
||||
check_resettable() |
||||
{ |
||||
local _target _override_resettable |
||||
|
||||
_override_resettable=$(kdump_get_conf_val override_resettable) |
||||
OVERRIDE_RESETTABLE=${_override_resettable:-$OVERRIDE_RESETTABLE} |
||||
if [ "$OVERRIDE_RESETTABLE" != "0" ] && [ "$OVERRIDE_RESETTABLE" != "1" ]; then |
||||
perror_exit "override_resettable value '$OVERRIDE_RESETTABLE' is invalid" |
||||
fi |
||||
|
||||
for_each_block_target is_unresettable && return |
||||
|
||||
return 1 |
||||
} |
||||
|
||||
check_crypt() |
||||
{ |
||||
local _dev |
||||
|
||||
for _dev in $(get_kdump_targets); do |
||||
if [[ -n $(get_luks_crypt_dev "$(get_maj_min "$_dev")") ]]; then |
||||
derror "Device $_dev is encrypted." && return 1 |
||||
fi |
||||
done |
||||
} |
||||
|
||||
if ! check_resettable; then |
||||
exit 1 |
||||
fi |
||||
|
||||
if ! check_crypt; then |
||||
dwarn "Warning: Encrypted device is in dump path, which is not recommended, see kexec-kdump-howto.txt for more details." |
||||
fi |
||||
|
||||
# firstly get right SSH_KEY_LOCATION |
||||
keyfile=$(kdump_get_conf_val sshkey) |
||||
if [[ -f $keyfile ]]; then |
||||
# canonicalize the path |
||||
SSH_KEY_LOCATION=$(/usr/bin/readlink -m "$keyfile") |
||||
fi |
||||
|
||||
while read -r config_opt config_val; do |
||||
# remove inline comments after the end of a directive. |
||||
case "$config_opt" in |
||||
extra_modules) |
||||
extra_modules="$extra_modules $config_val" |
||||
;; |
||||
ext[234] | xfs | btrfs | minix | nfs) |
||||
check_user_configured_target "$config_val" "$config_opt" |
||||
add_mount "$config_val" "$config_opt" |
||||
;; |
||||
raw) |
||||
# checking raw disk writable |
||||
dd if="$config_val" count=1 of=/dev/null > /dev/null 2>&1 || { |
||||
perror_exit "Bad raw disk $config_val" |
||||
} |
||||
_praw=$(persistent_policy="by-id" kdump_get_persistent_dev "$config_val") |
||||
if [[ -z $_praw ]]; then |
||||
exit 1 |
||||
fi |
||||
add_dracut_arg "--device" "$_praw" |
||||
check_size raw "$config_val" |
||||
;; |
||||
ssh) |
||||
if strstr "$config_val" "@"; then |
||||
mkdir_save_path_ssh "$config_val" |
||||
check_size ssh "$config_val" |
||||
add_dracut_sshkey "$SSH_KEY_LOCATION" |
||||
else |
||||
perror_exit "Bad ssh dump target $config_val" |
||||
fi |
||||
;; |
||||
core_collector) |
||||
verify_core_collector "$config_val" |
||||
;; |
||||
dracut_args) |
||||
while read -r dracut_arg; do |
||||
add_dracut_arg "$dracut_arg" |
||||
done <<< "$(echo "$config_val" | xargs -n 1 echo)" |
||||
;; |
||||
*) ;; |
||||
|
||||
esac |
||||
done <<< "$(kdump_read_conf)" |
||||
|
||||
handle_default_dump_target |
||||
|
||||
if ! have_compression_in_dracut_args; then |
||||
# Here zstd is set as the default compression method. If squash module |
||||
# is available for dracut, libzstd will be used by mksquashfs. If |
||||
# squash module is unavailable, command zstd will be used instead. |
||||
if is_squash_available || is_zstd_command_available; then |
||||
add_dracut_arg "--compress" "zstd" |
||||
fi |
||||
fi |
||||
|
||||
if [[ -n $extra_modules ]]; then |
||||
add_dracut_arg "--add-drivers" "$extra_modules" |
||||
fi |
||||
|
||||
# TODO: The below check is not needed anymore with the introduction of |
||||
# 'zz-fadumpinit' module, that isolates fadump's capture kernel initrd, |
||||
# but still sysroot.mount unit gets generated based on 'root=' kernel |
||||
# parameter available in fadump case. So, find a way to fix that first |
||||
# before removing this check. |
||||
if ! is_fadump_capable; then |
||||
# The 2nd rootfs mount stays behind the normal dump target mount, |
||||
# so it doesn't affect the logic of check_dump_fs_modified(). |
||||
is_dump_to_rootfs && add_mount "$(to_dev_name "$(get_root_fs_device)")" |
||||
|
||||
add_dracut_arg "--no-hostonly-default-device" |
||||
fi |
||||
|
||||
# This is RHEL-only to work around nvme problem, then real fix should go to dracut |
||||
if [[ -d /sys/module/nvme ]]; then |
||||
add_dracut_arg "--add-drivers" "nvme" |
||||
fi |
||||
|
||||
dracut "${dracut_args[@]}" "$@" |
||||
|
||||
_rc=$? |
||||
sync |
||||
exit $_rc |
||||
@ -0,0 +1,39 @@
@@ -0,0 +1,39 @@
|
||||
.TH MKDUMRD 8 "Fri Feb 9 2007" |
||||
.SH NAME |
||||
mkdumprd \- creates initial ramdisk images for kdump crash recovery |
||||
.SH SYNOPSIS |
||||
\fBmkdumprd\fR [OPTION] |
||||
|
||||
.SH DESCRIPTION |
||||
\fBmkdumprd\fR creates an initial ram file system for use in conjunction with |
||||
the booting of a kernel within the kdump framework for crash recovery. |
||||
\fBmkdumprds\fR purpose is to create an initial ram filesystem capable of copying |
||||
the crashed systems vmcore image to a location specified in \fI/etc/kdump.conf |
||||
|
||||
\fBmkdumprd\fR interrogates the running system to understand what modules need to |
||||
be loaded in the initramfs (based on configuration retrieved from |
||||
\fI/etc/kdump.conf)\fR |
||||
|
||||
\fBmkdumprd\fR add a new \fBdracut\fR module 99kdumpbase and use \fBdracut\fR |
||||
utility to generate the initramfs. When generating a kdump initramfs, \fBmkdumprd\fR |
||||
will determine how much disk space is available, if the dump target's available |
||||
space is not greater than the total system memory, \fBmkdumprd\fR will print a |
||||
warning to remind that there might not be enough space to save a vmcore. The |
||||
warning covers extreme scenarios such as the slab explodes with non-zero data or |
||||
a full vmcore, etc. Therefore, need to prevent users from having minimum disk |
||||
space for crash dump. |
||||
|
||||
\fBmkdumprd\fR was not intended for casual use outside of the service |
||||
initialization script for the kdump utility, and should not be run manually. If |
||||
you require a custom kdump initramfs image, it is suggested that you use the |
||||
kdump service infrastructure to create one, and then manually unpack, modify and |
||||
repack the image. |
||||
|
||||
|
||||
.SH OPTIONS |
||||
.TP |
||||
All options here are passed to dracut directly, please refer \fBdracut\fR docs |
||||
for the info. |
||||
|
||||
.SH "SEE ALSO" |
||||
.BR dracut (8) |
||||
@ -0,0 +1,74 @@
@@ -0,0 +1,74 @@
|
||||
#!/bin/bash --norc |
||||
# Generate an initramfs image that isolates dump capture capability within |
||||
# the default initramfs using zz-fadumpinit dracut module. |
||||
|
||||
if [[ -f /etc/sysconfig/kdump ]]; then |
||||
. /etc/sysconfig/kdump |
||||
fi |
||||
|
||||
[[ $dracutbasedir ]] || dracutbasedir=/usr/lib/dracut |
||||
. $dracutbasedir/dracut-functions.sh |
||||
. /lib/kdump/kdump-lib.sh |
||||
. /lib/kdump/kdump-logger.sh |
||||
|
||||
#initiate the kdump logger |
||||
if ! dlog_init; then |
||||
echo "mkfadumprd: failed to initiate the kdump logger." |
||||
exit 1 |
||||
fi |
||||
|
||||
MKFADUMPRD_TMPDIR="$(mktemp -d -t mkfadumprd.XXXXXX)" |
||||
[ -d "$MKFADUMPRD_TMPDIR" ] || perror_exit "mkfadumprd: mktemp -d -t mkfadumprd.XXXXXX failed." |
||||
trap ' |
||||
ret=$?; |
||||
[[ -d $MKFADUMPRD_TMPDIR ]] && rm --one-file-system -rf -- "$MKFADUMPRD_TMPDIR"; |
||||
exit $ret; |
||||
' EXIT |
||||
|
||||
# clean up after ourselves no matter how we die. |
||||
trap 'exit 1;' SIGINT |
||||
|
||||
MKDUMPRD="/sbin/mkdumprd -f" |
||||
# Default boot initramfs to be rebuilt |
||||
REBUILD_INITRD="$1" && shift |
||||
TARGET_INITRD="$1" && shift |
||||
FADUMP_INITRD="$MKFADUMPRD_TMPDIR/fadump.img" |
||||
|
||||
### First build an initramfs with dump capture capability |
||||
# this file tells the initrd is fadump enabled |
||||
touch "$MKFADUMPRD_TMPDIR/fadump.initramfs" |
||||
ddebug "rebuild fadump initrd: $FADUMP_INITRD $DEFAULT_INITRD $KDUMP_KERNELVER" |
||||
if ! $MKDUMPRD "$FADUMP_INITRD" -i "$MKFADUMPRD_TMPDIR/fadump.initramfs" /etc/fadump.initramfs; then |
||||
perror_exit "mkfadumprd: failed to build image with dump capture support" |
||||
fi |
||||
|
||||
### Unpack the initramfs having dump capture capability |
||||
mkdir -p "$MKFADUMPRD_TMPDIR/fadumproot" |
||||
if ! (pushd "$MKFADUMPRD_TMPDIR/fadumproot" > /dev/null && lsinitrd --unpack "$FADUMP_INITRD" && |
||||
popd > /dev/null); then |
||||
derror "mkfadumprd: failed to unpack '$MKFADUMPRD_TMPDIR'" |
||||
exit 1 |
||||
fi |
||||
|
||||
### Pack it into the normal boot initramfs with zz-fadumpinit module |
||||
_dracut_isolate_args=( |
||||
--rebuild "$REBUILD_INITRD" --add zz-fadumpinit |
||||
-i "$MKFADUMPRD_TMPDIR/fadumproot" /fadumproot |
||||
-i "$MKFADUMPRD_TMPDIR/fadumproot/usr/lib/dracut/hostonly-kernel-modules.txt" |
||||
/usr/lib/dracut/fadump-kernel-modules.txt |
||||
) |
||||
|
||||
if is_squash_available; then |
||||
_dracut_isolate_args+=(--add squash) |
||||
fi |
||||
|
||||
# Same as setting zstd in mkdumprd |
||||
if ! have_compression_in_dracut_args; then |
||||
if is_squash_available || is_zstd_command_available; then |
||||
_dracut_isolate_args+=(--compress zstd) |
||||
fi |
||||
fi |
||||
|
||||
if ! dracut --force --quiet "${_dracut_isolate_args[@]}" "$@" "$TARGET_INITRD"; then |
||||
perror_exit "mkfadumprd: failed to setup '$TARGET_INITRD' with dump capture capability" |
||||
fi |
||||
@ -0,0 +1,119 @@
@@ -0,0 +1,119 @@
|
||||
Supported Kdump Targets |
||||
|
||||
This document try to list all supported kdump targets, and those supported |
||||
or unknown/tech-preview targets, this can help users to decide whether a dump |
||||
solution is available. |
||||
|
||||
Dump Target support status |
||||
========================== |
||||
This section tries to come up with some kind of guidelines in terms of |
||||
what dump targets are supported/not supported. Whatever is listed here |
||||
is not binding in any manner. It is just sharing of current understanding |
||||
and if something is not right, this section needs to be edited. |
||||
|
||||
Following are 3 lists. First one contains supported targets. These are |
||||
generic configurations which should work and some configuration most |
||||
likely has worked in testing. Second list is known unsupported targets. |
||||
These targets we know either don't work or we don't support. And third |
||||
list is unknown/tech-preview. We either don't yet know the status of kdump |
||||
on these targets or these are under tech-preview. |
||||
|
||||
Note, these lists are not set in stone and can be changed at any point of |
||||
time. Also these lists might not be complete. We will add/remove items to |
||||
it as we get more testing information. Also, there are many corner cases |
||||
which can't possibly be listed. For example in general we might be |
||||
supporting software iscsi but there might be some configurations of it |
||||
which don't work. |
||||
|
||||
So if any target is listed in supported section, it does not mean it works |
||||
in all possible configurations. It just means that in common configurations |
||||
it should work but there can be issues with particular configurations which |
||||
are not supported. As we come to know of particular issues, we will keep on |
||||
updating lists accordingly. |
||||
|
||||
|
||||
Supported Dump targets |
||||
---------------------- |
||||
storage: |
||||
LVM volume (no thinp) |
||||
FC disks (qla2xxx, lpfc, bnx2fc, bfa) |
||||
software initiator based iSCSI |
||||
software RAID (mdraid) |
||||
hardware RAID (smartpqi, hpsa, megaraid, mpt3sas, aacraid, mpi3mr) |
||||
SCSI/SATA disks |
||||
iSCSI HBA (all offload) |
||||
hardware FCoE (qla2xxx, lpfc) |
||||
software FCoE (bnx2fc) (Extra configuration required, |
||||
please read "Note on FCoE" section below) |
||||
|
||||
network: |
||||
Hardware using kernel modules: (igb, ixgbe, ice, i40e, e1000e, igc, |
||||
tg3, bnx2x, bnxt_en, qede, cxgb4, be2net, enic, sfc, mlx4_en, |
||||
mlx5_core, r8169, atlantic, nfp, ionic; nicvf (aarch64 only)) |
||||
protocol: ipv4 |
||||
bonding |
||||
vlan |
||||
bridge |
||||
vlan tagged bonding |
||||
bridge over bond/vlan |
||||
|
||||
hypervisor: |
||||
kvm |
||||
xen (Supported in select configurations only) |
||||
|
||||
filesystem: |
||||
ext[234] |
||||
xfs |
||||
nfs |
||||
|
||||
firmware: |
||||
BIOS |
||||
UEFI |
||||
|
||||
hypervisor: |
||||
VMWare ESXi 4.x 5.x would not be tested/supported any more. |
||||
only support ESXi 6.6, 6.7, 7.0 |
||||
Hyper-V 2012 R2 (RHEL Gen1 UP Guest only), later version will |
||||
also be tested/supported |
||||
|
||||
Unsupported Dump targets |
||||
------------------------ |
||||
storage: |
||||
BIOS RAID |
||||
Thin provisioning volume |
||||
Software iSCSI with iBFT (bnx2i, cxgb3i, cxgb4i) |
||||
Software iSCSI with hybrid (be2iscsi) |
||||
FCoE |
||||
legacy IDE |
||||
glusterfs |
||||
gfs2/clvm/halvm |
||||
|
||||
network: |
||||
hardware using kernel modules: (sfc SRIOV, cxgb4vf, pch_gbe) |
||||
protocol: ipv6 |
||||
wireless |
||||
Infiniband (IB) |
||||
vlan over bridge/team |
||||
|
||||
filesystem: |
||||
btrfs |
||||
|
||||
Unknown/tech-preview |
||||
-------------------- |
||||
storage: |
||||
PCI Express based SSDs |
||||
|
||||
hypervisor: |
||||
Hyper-V 2008 |
||||
Hyper-V 2012 |
||||
|
||||
|
||||
Note on FCoE |
||||
===================== |
||||
If you are trying to dump to a software FCoE target, you may encounter OOM |
||||
issue, because some software FCoE requires more memory to work. In such case, |
||||
you may need to increase the kdump reserved memory size in "crashkernel=" |
||||
kernel parameter. |
||||
|
||||
For hardware FCoE, kdump should work naturally as firmware will do the |
||||
initialization job. The capture kernel and kdump tools will run just fine. |
||||
Loading…
Reference in new issue