2017-05-09 09:30:30 +00:00
|
|
|
#!/bin/bash
|
2011-07-06 19:25:34 +00:00
|
|
|
KEXEC=/sbin/kexec
|
|
|
|
|
|
|
|
KDUMP_KERNELVER=""
|
2020-07-27 18:40:20 +00:00
|
|
|
KDUMP_KERNEL=""
|
2011-07-06 19:25:34 +00:00
|
|
|
KDUMP_COMMANDLINE=""
|
|
|
|
KEXEC_ARGS=""
|
2020-10-27 09:04:24 +00:00
|
|
|
KDUMP_LOG_PATH="/var/log"
|
2012-06-06 08:24:23 +00:00
|
|
|
MKDUMPRD="/sbin/mkdumprd -f"
|
2021-06-23 14:36:48 +00:00
|
|
|
MKFADUMPRD="/sbin/mkfadumprd"
|
2017-08-31 06:27:00 +00:00
|
|
|
DRACUT_MODULES_FILE="/usr/lib/dracut/modules.txt"
|
2012-02-22 03:16:09 +00:00
|
|
|
SAVE_PATH=/var/crash
|
|
|
|
SSH_KEY_LOCATION="/root/.ssh/kdump_id_rsa"
|
2016-11-03 18:46:31 +00:00
|
|
|
INITRD_CHECKSUM_LOCATION="/boot/.fadump_initrd_checksum"
|
2012-02-22 03:16:09 +00:00
|
|
|
DUMP_TARGET=""
|
2016-11-03 18:46:31 +00:00
|
|
|
DEFAULT_INITRD=""
|
|
|
|
DEFAULT_INITRD_BAK=""
|
2020-07-27 18:40:20 +00:00
|
|
|
KDUMP_INITRD=""
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
TARGET_INITRD=""
|
2014-07-24 18:38:36 +00:00
|
|
|
FADUMP_REGISTER_SYS_NODE="/sys/kernel/fadump_registered"
|
|
|
|
#kdump shall be the default dump mode
|
|
|
|
DEFAULT_DUMP_MODE="kdump"
|
2016-05-09 08:17:53 +00:00
|
|
|
image_time=0
|
2011-07-06 19:25:34 +00:00
|
|
|
|
2020-10-27 09:04:24 +00:00
|
|
|
standard_kexec_args="-d -p"
|
2011-07-06 19:25:34 +00:00
|
|
|
|
2015-11-18 08:00:22 +00:00
|
|
|
# Some default values in case /etc/sysconfig/kdump doesn't include
|
|
|
|
KDUMP_COMMANDLINE_REMOVE="hugepages hugepagesz slub_debug"
|
|
|
|
|
2011-07-06 19:25:34 +00:00
|
|
|
if [ -f /etc/sysconfig/kdump ]; then
|
|
|
|
. /etc/sysconfig/kdump
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
[[ $dracutbasedir ]] || dracutbasedir=/usr/lib/dracut
|
|
|
|
. $dracutbasedir/dracut-functions.sh
|
|
|
|
. /lib/kdump/kdump-lib.sh
|
2021-01-19 12:10:28 +00:00
|
|
|
. /lib/kdump/kdump-logger.sh
|
2020-10-27 09:04:22 +00:00
|
|
|
|
|
|
|
#initiate the kdump logger
|
|
|
|
dlog_init
|
|
|
|
if [ $? -ne 0 ]; then
|
|
|
|
echo "failed to initiate the kdump logger."
|
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
|
2013-08-30 09:21:56 +00:00
|
|
|
single_instance_lock()
|
|
|
|
{
|
2014-07-16 12:09:48 +00:00
|
|
|
local rc timeout=5
|
|
|
|
|
2013-08-30 09:21:56 +00:00
|
|
|
exec 9>/var/lock/kdump
|
2017-07-12 02:59:55 +00:00
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Create file lock failed"
|
2017-07-12 02:59:55 +00:00
|
|
|
exit 1
|
|
|
|
fi
|
2014-07-16 12:09:48 +00:00
|
|
|
|
|
|
|
flock -n 9
|
|
|
|
rc=$?
|
|
|
|
|
|
|
|
while [ $rc -ne 0 ]; do
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Another app is currently holding the kdump lock; waiting for it to exit..."
|
2014-07-16 12:09:48 +00:00
|
|
|
flock -w $timeout 9
|
|
|
|
rc=$?
|
|
|
|
done
|
2013-08-30 09:21:56 +00:00
|
|
|
}
|
|
|
|
|
2014-07-24 18:38:36 +00:00
|
|
|
determine_dump_mode()
|
|
|
|
{
|
|
|
|
# Check if firmware-assisted dump is enabled
|
|
|
|
# if yes, set the dump mode as fadump
|
|
|
|
if is_fadump_capable; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Dump mode is fadump"
|
2014-07-24 18:38:36 +00:00
|
|
|
DEFAULT_DUMP_MODE="fadump"
|
|
|
|
fi
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "DEFAULT_DUMP_MODE=$DEFAULT_DUMP_MODE"
|
2014-07-24 18:38:36 +00:00
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
save_core()
|
2011-07-06 19:25:34 +00:00
|
|
|
{
|
|
|
|
coredir="/var/crash/`date +"%Y-%m-%d-%H:%M"`"
|
|
|
|
|
|
|
|
mkdir -p $coredir
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "cp --sparse=always /proc/vmcore $coredir/vmcore-incomplete"
|
2011-07-06 19:25:34 +00:00
|
|
|
cp --sparse=always /proc/vmcore $coredir/vmcore-incomplete
|
|
|
|
if [ $? == 0 ]; then
|
|
|
|
mv $coredir/vmcore-incomplete $coredir/vmcore
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "saved a vmcore to $coredir"
|
2011-07-06 19:25:34 +00:00
|
|
|
else
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "failed to save a vmcore to $coredir"
|
2011-07-06 19:25:34 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
# pass the dmesg to Abrt tool if exists, in order
|
|
|
|
# to collect the kernel oops message.
|
|
|
|
# https://fedorahosted.org/abrt/
|
|
|
|
if [ -x /usr/bin/dumpoops ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "makedumpfile --dump-dmesg $coredir/vmcore $coredir/dmesg"
|
2011-07-06 19:25:34 +00:00
|
|
|
makedumpfile --dump-dmesg $coredir/vmcore $coredir/dmesg >/dev/null 2>&1
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "dumpoops -d $coredir/dmesg"
|
2011-07-06 19:25:34 +00:00
|
|
|
dumpoops -d $coredir/dmesg >/dev/null 2>&1
|
|
|
|
if [ $? == 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "kernel oops has been collected by abrt tool"
|
2011-07-06 19:25:34 +00:00
|
|
|
fi
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
rebuild_fadump_initrd()
|
2012-06-14 01:57:27 +00:00
|
|
|
{
|
2021-06-23 14:36:48 +00:00
|
|
|
if ! $MKFADUMPRD "$DEFAULT_INITRD_BAK" "$TARGET_INITRD" --kver "$KDUMP_KERNELVER"; then
|
|
|
|
derror "mkfadumprd: failed to make fadump initrd"
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2019-05-16 05:09:21 +00:00
|
|
|
check_earlykdump_is_enabled()
|
|
|
|
{
|
|
|
|
grep -q -w "rd.earlykdump" /proc/cmdline
|
|
|
|
return $?
|
|
|
|
}
|
|
|
|
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
rebuild_kdump_initrd()
|
|
|
|
{
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "rebuild kdump initrd: $MKDUMPRD $TARGET_INITRD $KDUMP_KERNELVER"
|
2020-07-27 18:40:20 +00:00
|
|
|
$MKDUMPRD $TARGET_INITRD $KDUMP_KERNELVER
|
2012-06-14 01:57:27 +00:00
|
|
|
if [ $? != 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "mkdumprd: failed to make kdump initrd"
|
2012-06-14 01:57:27 +00:00
|
|
|
return 1
|
|
|
|
fi
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
|
2019-05-16 05:09:21 +00:00
|
|
|
if check_earlykdump_is_enabled; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "Tips: If early kdump is enabled, also require rebuilding the system initramfs to make the changes take effect for early kdump."
|
2019-05-16 05:09:21 +00:00
|
|
|
fi
|
|
|
|
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
rebuild_initrd()
|
|
|
|
{
|
2021-04-16 22:31:13 +00:00
|
|
|
if [[ ! -w $(dirname $TARGET_INITRD) ]];then
|
|
|
|
derror "$(dirname $TARGET_INITRD) does not have write permission. Cannot rebuild $TARGET_INITRD"
|
2019-03-29 03:29:30 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
if [ $DEFAULT_DUMP_MODE == "fadump" ]; then
|
|
|
|
rebuild_fadump_initrd
|
|
|
|
else
|
|
|
|
rebuild_kdump_initrd
|
|
|
|
fi
|
|
|
|
|
|
|
|
return $?
|
2012-06-14 01:57:27 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
#$1: the files to be checked with IFS=' '
|
2014-07-15 06:41:54 +00:00
|
|
|
check_exist()
|
2012-06-14 01:57:27 +00:00
|
|
|
{
|
|
|
|
for file in $1; do
|
2020-07-29 07:52:21 +00:00
|
|
|
if [ ! -e "$file" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Error: $file not found."
|
2012-06-14 01:57:27 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
}
|
|
|
|
|
|
|
|
#$1: the files to be checked with IFS=' '
|
2014-07-15 06:41:54 +00:00
|
|
|
check_executable()
|
2012-06-14 01:57:27 +00:00
|
|
|
{
|
|
|
|
for file in $1; do
|
|
|
|
if [ ! -x "$file" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Error: $file is not executable."
|
2012-06-14 01:57:27 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
}
|
|
|
|
|
2016-11-03 18:46:31 +00:00
|
|
|
backup_default_initrd()
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
{
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "backup default initrd: $DEFAULT_INITRD"
|
|
|
|
|
2017-05-04 06:56:54 +00:00
|
|
|
if [ ! -f "$DEFAULT_INITRD" ]; then
|
|
|
|
return
|
|
|
|
fi
|
|
|
|
|
2016-11-03 18:46:31 +00:00
|
|
|
if [ ! -e $DEFAULT_INITRD_BAK ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Backing up $DEFAULT_INITRD before rebuild."
|
2016-11-03 18:46:31 +00:00
|
|
|
# save checksum to verify before restoring
|
|
|
|
sha1sum $DEFAULT_INITRD > $INITRD_CHECKSUM_LOCATION
|
|
|
|
cp $DEFAULT_INITRD $DEFAULT_INITRD_BAK
|
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "WARNING: failed to backup $DEFAULT_INITRD."
|
2016-11-03 18:46:31 +00:00
|
|
|
rm -f $DEFAULT_INITRD_BAK
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
}
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
|
2016-11-03 18:46:31 +00:00
|
|
|
restore_default_initrd()
|
|
|
|
{
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "restore default initrd: $DEFAULT_INITRD"
|
|
|
|
|
2020-07-27 18:40:20 +00:00
|
|
|
if [ ! -f "$DEFAULT_INITRD" ]; then
|
|
|
|
return
|
|
|
|
fi
|
|
|
|
|
2016-11-03 18:46:31 +00:00
|
|
|
# If a backup initrd exists, we must be switching back from
|
|
|
|
# fadump to kdump. Restore the original default initrd.
|
|
|
|
if [ -f $DEFAULT_INITRD_BAK ] && [ -f $INITRD_CHECKSUM_LOCATION ]; then
|
|
|
|
# verify checksum before restoring
|
2021-08-04 07:14:00 +00:00
|
|
|
backup_checksum=$(sha1sum "$DEFAULT_INITRD_BAK" | awk '{ print $1 }')
|
|
|
|
default_checksum=$(awk '{ print $1 }' "$INITRD_CHECKSUM_LOCATION")
|
2016-11-03 18:46:31 +00:00
|
|
|
if [ "$default_checksum" != "$backup_checksum" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "WARNING: checksum mismatch! Can't restore original initrd.."
|
2016-11-03 18:46:31 +00:00
|
|
|
else
|
|
|
|
rm -f $INITRD_CHECKSUM_LOCATION
|
|
|
|
mv $DEFAULT_INITRD_BAK $DEFAULT_INITRD
|
|
|
|
if [[ $? -eq 0 ]]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Restoring original initrd as fadump mode is disabled."
|
2016-11-03 18:46:31 +00:00
|
|
|
sync
|
|
|
|
fi
|
|
|
|
fi
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
check_config()
|
2013-03-11 09:31:25 +00:00
|
|
|
{
|
2020-08-20 17:35:20 +00:00
|
|
|
local -A _opt_rec
|
2021-04-14 05:41:19 +00:00
|
|
|
while read -r config_opt config_val; do
|
2013-03-11 09:31:25 +00:00
|
|
|
case "$config_opt" in
|
2020-08-20 17:35:20 +00:00
|
|
|
dracut_args)
|
|
|
|
if [[ $config_val == *--mount* ]]; then
|
|
|
|
if [ $(echo $config_val | grep -o "\-\-mount" | wc -l) -ne 1 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Multiple mount targets specified in one \"dracut_args\"."
|
2020-08-20 17:35:20 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
config_opt=_target
|
|
|
|
fi
|
2013-03-11 09:31:25 +00:00
|
|
|
;;
|
2020-08-20 17:35:20 +00:00
|
|
|
raw)
|
|
|
|
if [ -d "/proc/device-tree/ibm,opal/dump" ]; then
|
2020-10-27 09:34:48 +00:00
|
|
|
dwarn "WARNING: Won't capture opalcore when 'raw' dump target is used."
|
2020-01-28 19:34:48 +00:00
|
|
|
fi
|
2020-08-20 17:35:20 +00:00
|
|
|
config_opt=_target
|
|
|
|
;;
|
|
|
|
ext[234]|minix|btrfs|xfs|nfs|ssh)
|
|
|
|
config_opt=_target
|
|
|
|
;;
|
|
|
|
sshkey|path|core_collector|kdump_post|kdump_pre|extra_bins|extra_modules|failure_action|default|final_action|force_rebuild|force_no_rebuild|fence_kdump_args|fence_kdump_nodes)
|
2013-03-11 09:31:25 +00:00
|
|
|
;;
|
2013-03-22 03:55:24 +00:00
|
|
|
net|options|link_delay|disk_timeout|debug_mem_level|blacklist)
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Deprecated kdump config option: $config_opt. Refer to kdump.conf manpage for alternatives."
|
2013-03-11 09:31:25 +00:00
|
|
|
return 1
|
|
|
|
;;
|
2021-04-14 05:41:19 +00:00
|
|
|
'')
|
|
|
|
continue
|
|
|
|
;;
|
2013-03-11 09:31:25 +00:00
|
|
|
*)
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Invalid kdump config option $config_opt"
|
2020-08-20 17:35:20 +00:00
|
|
|
return 1
|
2013-03-11 09:31:25 +00:00
|
|
|
;;
|
|
|
|
esac
|
2020-08-20 17:35:20 +00:00
|
|
|
|
2021-04-14 05:41:19 +00:00
|
|
|
if [[ -z "$config_val" ]]; then
|
|
|
|
derror "Invalid kdump config value for option '$config_opt'"
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2020-08-20 17:35:20 +00:00
|
|
|
if [ -n "${_opt_rec[$config_opt]}" ]; then
|
|
|
|
if [ $config_opt == _target ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "More than one dump targets specified"
|
2020-08-20 17:35:20 +00:00
|
|
|
else
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Duplicated kdump config value of option $config_opt"
|
2020-08-20 17:35:20 +00:00
|
|
|
fi
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
_opt_rec[$config_opt]="$config_val"
|
2021-08-03 11:49:51 +00:00
|
|
|
done <<< "$(kdump_read_conf)"
|
2014-07-15 06:41:54 +00:00
|
|
|
|
2019-01-17 20:31:23 +00:00
|
|
|
check_failure_action_config || return 1
|
2019-01-17 20:31:24 +00:00
|
|
|
check_final_action_config || return 1
|
2014-04-02 08:33:47 +00:00
|
|
|
check_fence_kdump_config || return 1
|
|
|
|
|
2013-03-11 09:31:25 +00:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2014-04-02 08:33:47 +00:00
|
|
|
# get_pcs_cluster_modified_files <image timestamp>
|
|
|
|
# return list of modified file for fence_kdump modified in Pacemaker cluster
|
|
|
|
get_pcs_cluster_modified_files()
|
2013-12-17 07:00:33 +00:00
|
|
|
{
|
2014-04-02 08:33:47 +00:00
|
|
|
local time_stamp
|
|
|
|
local modified_files
|
2013-12-17 07:00:33 +00:00
|
|
|
|
2014-04-02 08:33:47 +00:00
|
|
|
is_generic_fence_kdump && return 1
|
2014-04-02 08:33:43 +00:00
|
|
|
is_pcs_fence_kdump || return 1
|
2013-12-17 07:00:33 +00:00
|
|
|
|
2014-04-02 08:33:47 +00:00
|
|
|
time_stamp=`pcs cluster cib | xmllint --xpath 'string(/cib/@cib-last-written)' - | \
|
|
|
|
xargs -0 date +%s --date`
|
2013-12-17 07:00:33 +00:00
|
|
|
|
2014-04-02 08:33:47 +00:00
|
|
|
if [ -n $time_stamp -a $time_stamp -gt $image_time ]; then
|
|
|
|
modified_files="cluster-cib"
|
2013-12-17 07:00:33 +00:00
|
|
|
fi
|
|
|
|
|
2014-04-02 08:33:47 +00:00
|
|
|
if [ -f $FENCE_KDUMP_CONFIG_FILE ]; then
|
|
|
|
time_stamp=`stat -c "%Y" $FENCE_KDUMP_CONFIG_FILE`
|
|
|
|
if [ "$time_stamp" -gt "$image_time" ]; then
|
|
|
|
modified_files="$modified_files $FENCE_KDUMP_CONFIG_FILE"
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
|
|
|
echo $modified_files
|
2013-12-17 07:00:33 +00:00
|
|
|
}
|
|
|
|
|
2016-11-03 18:46:31 +00:00
|
|
|
setup_initrd()
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
{
|
2020-07-27 18:40:20 +00:00
|
|
|
prepare_kdump_bootinfo
|
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "failed to prepare for kdump bootinfo."
|
2020-07-27 18:40:20 +00:00
|
|
|
return 1
|
2018-10-23 14:13:28 +00:00
|
|
|
fi
|
|
|
|
|
2020-07-27 18:40:20 +00:00
|
|
|
DEFAULT_INITRD_BAK="$KDUMP_BOOTDIR/.$(basename $DEFAULT_INITRD).default"
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
if [ $DEFAULT_DUMP_MODE == "fadump" ]; then
|
2016-11-03 18:46:31 +00:00
|
|
|
TARGET_INITRD="$DEFAULT_INITRD"
|
2019-03-29 03:29:30 +00:00
|
|
|
|
|
|
|
# backup initrd for reference before replacing it
|
|
|
|
# with fadump aware initrd
|
|
|
|
backup_default_initrd
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
else
|
2020-07-27 18:40:20 +00:00
|
|
|
TARGET_INITRD="$KDUMP_INITRD"
|
2019-03-29 03:29:30 +00:00
|
|
|
|
|
|
|
# check if a backup of default initrd exists. If yes,
|
|
|
|
# it signifies a switch from fadump mode. So, restore
|
|
|
|
# the backed up default initrd.
|
|
|
|
restore_default_initrd
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
2016-05-09 08:17:53 +00:00
|
|
|
check_files_modified()
|
|
|
|
{
|
|
|
|
local modified_files=""
|
|
|
|
|
|
|
|
#also rebuild when Pacemaker cluster conf is changed and fence kdump is enabled.
|
|
|
|
modified_files=$(get_pcs_cluster_modified_files)
|
|
|
|
|
2021-08-03 14:50:02 +00:00
|
|
|
EXTRA_BINS=$(kdump_get_conf_val kdump_post)
|
|
|
|
CHECK_FILES=$(kdump_get_conf_val kdump_pre)
|
2020-07-16 08:50:15 +00:00
|
|
|
HOOKS="/etc/kdump/post.d/ /etc/kdump/pre.d/"
|
2020-06-05 02:24:07 +00:00
|
|
|
if [ -d /etc/kdump/post.d ]; then
|
|
|
|
for file in /etc/kdump/post.d/*; do
|
|
|
|
if [ -x "$file" ]; then
|
|
|
|
POST_FILES="$POST_FILES $file"
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
fi
|
|
|
|
if [ -d /etc/kdump/pre.d ]; then
|
|
|
|
for file in /etc/kdump/pre.d/*; do
|
|
|
|
if [ -x "$file" ]; then
|
|
|
|
PRE_FILES="$PRE_FILES $file"
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
fi
|
2020-07-16 08:50:15 +00:00
|
|
|
HOOKS="$HOOKS $POST_FILES $PRE_FILES"
|
2021-08-03 14:50:02 +00:00
|
|
|
CORE_COLLECTOR=$(kdump_get_conf_val core_collector | awk '{print $1}')
|
2018-02-27 11:35:47 +00:00
|
|
|
CORE_COLLECTOR=`type -P $CORE_COLLECTOR`
|
2020-07-16 08:50:15 +00:00
|
|
|
# POST_FILES and PRE_FILES are already checked against executable, need not to check again.
|
|
|
|
EXTRA_BINS="$EXTRA_BINS $CHECK_FILES"
|
2021-08-03 14:50:02 +00:00
|
|
|
CHECK_FILES=$(kdump_get_conf_val extra_bins)
|
2016-05-09 08:17:53 +00:00
|
|
|
EXTRA_BINS="$EXTRA_BINS $CHECK_FILES"
|
2020-07-27 18:40:20 +00:00
|
|
|
files="$KDUMP_CONFIG_FILE $KDUMP_KERNEL $EXTRA_BINS $CORE_COLLECTOR"
|
2016-09-14 14:42:17 +00:00
|
|
|
[[ -e /etc/fstab ]] && files="$files /etc/fstab"
|
2016-05-09 08:17:53 +00:00
|
|
|
|
2019-05-13 06:20:25 +00:00
|
|
|
# Check for any updated extra module
|
2021-08-03 14:50:02 +00:00
|
|
|
EXTRA_MODULES="$(kdump_get_conf_val extra_modules)"
|
2019-05-13 06:20:25 +00:00
|
|
|
if [ -n "$EXTRA_MODULES" ]; then
|
2020-07-27 18:40:20 +00:00
|
|
|
if [ -e /lib/modules/$KDUMP_KERNELVER/modules.dep ]; then
|
|
|
|
files="$files /lib/modules/$KDUMP_KERNELVER/modules.dep"
|
2019-05-13 06:20:25 +00:00
|
|
|
fi
|
|
|
|
for _module in $EXTRA_MODULES; do
|
2020-07-27 18:40:20 +00:00
|
|
|
_module_file="$(modinfo --set-version "$KDUMP_KERNELVER" --filename "$_module" 2>/dev/null)"
|
2019-05-13 06:20:25 +00:00
|
|
|
if [[ $? -eq 0 ]]; then
|
|
|
|
files="$files $_module_file"
|
|
|
|
for _dep_modules in $(modinfo -F depends $_module | tr ',' ' '); do
|
2020-07-27 18:40:20 +00:00
|
|
|
files="$files $(modinfo --set-version "$KDUMP_KERNELVER" --filename $_dep_modules 2>/dev/null)"
|
2019-05-13 06:20:25 +00:00
|
|
|
done
|
|
|
|
else
|
|
|
|
# If it's not a module nor builtin, give an error
|
2020-07-27 18:40:20 +00:00
|
|
|
if ! ( modprobe --set-version "$KDUMP_KERNELVER" --dry-run "$_module" &>/dev/null ); then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "Module $_module not found"
|
2019-05-13 06:20:25 +00:00
|
|
|
fi
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
fi
|
|
|
|
|
2020-07-29 07:52:21 +00:00
|
|
|
# HOOKS is mandatory and need to check the modification time
|
|
|
|
files="$files $HOOKS"
|
2016-05-09 08:17:53 +00:00
|
|
|
check_exist "$files" && check_executable "$EXTRA_BINS"
|
|
|
|
[ $? -ne 0 ] && return 2
|
|
|
|
|
|
|
|
for file in $files; do
|
2019-05-13 06:20:24 +00:00
|
|
|
if [ -e "$file" ]; then
|
|
|
|
time_stamp=`stat -c "%Y" $file`
|
|
|
|
if [ "$time_stamp" -gt "$image_time" ]; then
|
|
|
|
modified_files="$modified_files $file"
|
|
|
|
fi
|
|
|
|
if [ -L "$file" ]; then
|
|
|
|
file=$(readlink -m $file)
|
|
|
|
time_stamp=`stat -c "%Y" $file`
|
|
|
|
if [ "$time_stamp" -gt "$image_time" ]; then
|
|
|
|
modified_files="$modified_files $file"
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
else
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "$file doesn't exist"
|
2016-05-09 08:17:53 +00:00
|
|
|
fi
|
|
|
|
done
|
2019-05-13 06:20:24 +00:00
|
|
|
|
2016-05-09 08:17:53 +00:00
|
|
|
if [ -n "$modified_files" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Detected change(s) in the following file(s): $modified_files"
|
2016-05-09 08:17:53 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2020-10-15 10:22:12 +00:00
|
|
|
check_drivers_modified()
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
{
|
2020-10-15 10:22:12 +00:00
|
|
|
local _target _new_drivers _old_drivers _module_name _module_filename
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
|
2020-10-15 10:22:12 +00:00
|
|
|
# If it's dump target is on block device, detect the block driver
|
|
|
|
_target=$(get_block_dump_target)
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
if [[ -n "$_target" ]]; then
|
2020-10-15 10:22:12 +00:00
|
|
|
_record_block_drivers() {
|
|
|
|
local _drivers
|
|
|
|
_drivers=$(udevadm info -a "/dev/block/$1" | sed -n 's/\s*DRIVERS=="\(\S\+\)"/\1/p')
|
|
|
|
for _driver in $_drivers; do
|
|
|
|
if ! [[ " $_new_drivers " == *" $_driver "* ]]; then
|
|
|
|
_new_drivers="$_new_drivers $_driver"
|
|
|
|
fi
|
|
|
|
done
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
|
2020-10-15 10:22:12 +00:00
|
|
|
ddebug "MAJ:MIN=$1 drivers='$_drivers'"
|
|
|
|
}
|
|
|
|
check_block_and_slaves_all _record_block_drivers "$(get_maj_min "$_target")"
|
|
|
|
fi
|
2020-10-27 09:04:22 +00:00
|
|
|
|
2020-10-15 10:22:14 +00:00
|
|
|
# Include watchdog drivers if watchdog module is not omitted
|
2020-10-15 10:22:15 +00:00
|
|
|
is_dracut_mod_omitted watchdog || _new_drivers+=" $(get_watchdog_drvs)"
|
2020-10-15 10:22:12 +00:00
|
|
|
[ -z "$_new_drivers" ] && return 0
|
2021-06-25 06:44:45 +00:00
|
|
|
|
|
|
|
if is_fadump_capable; then
|
|
|
|
_old_drivers="$(lsinitrd "$TARGET_INITRD" -f /usr/lib/dracut/fadump-kernel-modules.txt | tr '\n' ' ')"
|
|
|
|
else
|
|
|
|
_old_drivers="$(lsinitrd "$TARGET_INITRD" -f /usr/lib/dracut/hostonly-kernel-modules.txt | tr '\n' ' ')"
|
|
|
|
fi
|
2020-10-27 09:04:22 +00:00
|
|
|
|
2020-10-15 10:22:14 +00:00
|
|
|
ddebug "Modules required for kdump: '$_new_drivers'"
|
2020-10-15 10:22:12 +00:00
|
|
|
ddebug "Modules included in old initramfs: '$_old_drivers'"
|
|
|
|
for _driver in $_new_drivers; do
|
2020-03-18 07:51:21 +00:00
|
|
|
# Skip deprecated/invalid driver name or built-in module
|
2020-07-27 18:40:20 +00:00
|
|
|
_module_name=$(modinfo --set-version "$KDUMP_KERNELVER" -F name $_driver 2>/dev/null)
|
|
|
|
_module_filename=$(modinfo --set-version "$KDUMP_KERNELVER" -n $_driver 2>/dev/null)
|
2020-03-18 07:51:21 +00:00
|
|
|
if [ $? -ne 0 ] || [ -z "$_module_name" ] || [[ "$_module_filename" = *"(builtin)"* ]]; then
|
kdumpctl: Detect block device driver change for initramfs rebuild
Previous we rebuild the initramfs when kenrel load module list changed,
but this is not very stable as some async services may load/unload
kernel modules, and cause unnecessary initramfs rebuild.
Instead, it's better to just check if the module required to dump to
the dump target is loaded or not, and rebuild if not loaded. This
avoids most false-positives, and ensure local target change is always
covered.
Currently only local fs dump target is covered, because this check
requires the dump target to be mounted when building the initramfs,
this guarantee that the module is in the loaded kernel module list,
else we may still get some false positive.
dracut-install could be leveraged to combine the modalias list with
kernel loaded module list as a more stable module list in the initramfs,
but upstream dracut change need to be done first.
Passed test on a KVM VM, changing the storage between SATA/USB/VirtIO
will trigger initramfs rebuild and didn't notice any false-positive.
Also passed test on my laptop with no false-positive.
Signed-off-by: Kairui Song <kasong@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2019-05-07 06:19:18 +00:00
|
|
|
continue
|
|
|
|
fi
|
|
|
|
if ! [[ " $_old_drivers " == *" $_module_name "* ]]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Detected change in block device driver, new loaded module: $_module_name"
|
kdumpctl: Detect block device driver change for initramfs rebuild
Previous we rebuild the initramfs when kenrel load module list changed,
but this is not very stable as some async services may load/unload
kernel modules, and cause unnecessary initramfs rebuild.
Instead, it's better to just check if the module required to dump to
the dump target is loaded or not, and rebuild if not loaded. This
avoids most false-positives, and ensure local target change is always
covered.
Currently only local fs dump target is covered, because this check
requires the dump target to be mounted when building the initramfs,
this guarantee that the module is in the loaded kernel module list,
else we may still get some false positive.
dracut-install could be leveraged to combine the modalias list with
kernel loaded module list as a more stable module list in the initramfs,
but upstream dracut change need to be done first.
Passed test on a KVM VM, changing the storage between SATA/USB/VirtIO
will trigger initramfs rebuild and didn't notice any false-positive.
Also passed test on my laptop with no false-positive.
Signed-off-by: Kairui Song <kasong@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2019-05-07 06:19:18 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
done
|
2020-10-15 10:22:12 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
check_fs_modified()
|
|
|
|
{
|
|
|
|
local _old_dev _old_mntpoint _old_fstype
|
|
|
|
local _new_dev _new_mntpoint _new_fstype
|
|
|
|
local _target _dracut_args
|
|
|
|
|
|
|
|
# No need to check in case of mount target specified via "dracut_args".
|
|
|
|
if is_mount_in_dracut_args; then
|
|
|
|
return 0
|
|
|
|
fi
|
kdumpctl: Detect block device driver change for initramfs rebuild
Previous we rebuild the initramfs when kenrel load module list changed,
but this is not very stable as some async services may load/unload
kernel modules, and cause unnecessary initramfs rebuild.
Instead, it's better to just check if the module required to dump to
the dump target is loaded or not, and rebuild if not loaded. This
avoids most false-positives, and ensure local target change is always
covered.
Currently only local fs dump target is covered, because this check
requires the dump target to be mounted when building the initramfs,
this guarantee that the module is in the loaded kernel module list,
else we may still get some false positive.
dracut-install could be leveraged to combine the modalias list with
kernel loaded module list as a more stable module list in the initramfs,
but upstream dracut change need to be done first.
Passed test on a KVM VM, changing the storage between SATA/USB/VirtIO
will trigger initramfs rebuild and didn't notice any false-positive.
Also passed test on my laptop with no false-positive.
Signed-off-by: Kairui Song <kasong@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2019-05-07 06:19:18 +00:00
|
|
|
|
2020-10-15 10:22:12 +00:00
|
|
|
# No need to check in case of raw target.
|
|
|
|
# Currently we do not check also if ssh/nfs target is specified
|
|
|
|
if is_ssh_dump_target || is_nfs_dump_target || is_raw_dump_target; then
|
|
|
|
return 0
|
|
|
|
fi
|
|
|
|
|
|
|
|
_target=$(get_block_dump_target)
|
|
|
|
_new_fstype=$(get_fs_type_from_target $_target)
|
|
|
|
if [[ -z "$_target" ]] || [[ -z "$_new_fstype" ]];then
|
|
|
|
derror "Dump target is invalid"
|
|
|
|
return 2
|
|
|
|
fi
|
|
|
|
|
|
|
|
ddebug "_target=$_target _new_fstype=$_new_fstype"
|
2020-11-30 07:16:57 +00:00
|
|
|
_new_dev=$(kdump_get_persistent_dev $_target)
|
|
|
|
if [ -z "$_new_dev" ]; then
|
|
|
|
perror "Get persistent device name failed"
|
|
|
|
return 2
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
fi
|
|
|
|
|
2020-03-05 15:28:53 +00:00
|
|
|
_new_mntpoint="$(get_kdump_mntpoint_from_target $_target)"
|
2017-05-04 06:56:56 +00:00
|
|
|
_dracut_args=$(lsinitrd $TARGET_INITRD -f usr/lib/dracut/build-parameter.txt)
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
if [[ -z "$_dracut_args" ]];then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "Warning: No dracut arguments found in initrd"
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
return 0
|
|
|
|
fi
|
|
|
|
|
|
|
|
# if --mount argument present then match old and new target, mount
|
|
|
|
# point and file system. If any of them mismatches then rebuild
|
2021-08-04 07:44:02 +00:00
|
|
|
echo $_dracut_args | grep -q "\-\-mount"
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
if [[ $? -eq 0 ]];then
|
|
|
|
set -- $(echo $_dracut_args | awk -F "--mount '" '{print $2}' | cut -d' ' -f1,2,3)
|
|
|
|
_old_dev=$1
|
|
|
|
_old_mntpoint=$2
|
|
|
|
_old_fstype=$3
|
|
|
|
[[ $_new_dev = $_old_dev && $_new_mntpoint = $_old_mntpoint && $_new_fstype = $_old_fstype ]] && return 0
|
|
|
|
# otherwise rebuild if target device is not a root device
|
|
|
|
else
|
|
|
|
[[ "$_target" = "$(get_root_fs_device)" ]] && return 0
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Detected change in File System"
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2016-05-09 08:17:52 +00:00
|
|
|
# returns 0 if system is not modified
|
|
|
|
# returns 1 if system is modified
|
|
|
|
# returns 2 if system modification is invalid
|
|
|
|
check_system_modified()
|
|
|
|
{
|
2016-05-09 08:17:53 +00:00
|
|
|
local ret
|
|
|
|
|
2016-05-09 08:17:52 +00:00
|
|
|
[[ -f $TARGET_INITRD ]] || return 1
|
|
|
|
|
2016-05-09 08:17:53 +00:00
|
|
|
check_files_modified
|
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ]; then
|
|
|
|
return $ret
|
|
|
|
fi
|
|
|
|
|
2020-10-15 10:22:12 +00:00
|
|
|
check_fs_modified
|
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ]; then
|
|
|
|
return $ret
|
|
|
|
fi
|
|
|
|
|
|
|
|
check_drivers_modified
|
kdumpctl: force rebuild in case of file system is modified
kdumpctl passes --device argument if dump target is a raw device. It passes
--mount argument if dump target is either mounted as nfs or as a bulk
device. When dump target device is a root device then it does not pass any
of the above two arguments.
After kdumpctl restart, if there is any change in file system which needs
different dracut arguments, then initramfs must be rebuild.
Modification in filesystem for a raw target does not affect dracut
arguments. So, we do not consider to check any modification if raw target
was specified in kdump.conf.
We might need to change dracut arguments if there is some changes in nfs
and ssh target related files. However, we do not consider them in this
patch.
We mainly consider changes in bulk target specified in kdump.conf. We also
consider changes in bulk and nfs file system, if there was no dump target
specified in kdump.conf but dump path is mounting such file systems.
So the initramfs must be rebuild if, either dump target's persistent path
or it's mount point or its file system type changes. If there is no dump
target specified then, both dump path and root path must mount same device,
otherwise rebuild should be triggered.
Some of the examples when we can need a rebuild:
-- "dump target" is specified as one of ext[234], xfs or btrfs. But after
kdump initramfs building its UUID is changed by reformatting.
-- "dump target" is specified as file system type fs1 (say ext3). But after
kdump initramfs building, user change it to fs2 (say ext4), probably by
a mkfs.ext4 executing on the target device.
-- "dump target" is not specified, but "dump path" mounts a device which
is different than device for root path and either UUID or file system type
is modified after kdump initramfs build.
-- "dump target" is not specified, but "dump path" mounts a nfs device and
nfs host path changes after kdump initramfs build.
Some testing:
Initial conditions:
-- No dump target specified
-- dump path (/var/crash) and root(/) are on same device
-- kdumpctl was already executed once after last modification in
/etc/kdump.conf
# kdumpctl restart
No rebuild
# mkfs.ext2 /dev/md0;mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/md0;
# mount /dev/md0 /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.ext4 /dev/mapper/fedora-swap
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.btrfs /dev/mapper/fedora-swap -f
# mount /dev/mapper/fedora-swap /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount /dev/mapper/fedora-swap /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash;mkfs.minix /dev/md0
# mount /dev/md0 /var/crash/; kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# mount 192.168.1.16:/nfsroot /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
# kdumpctl restart
No rebuild
# umount /var/crash;mount 192.168.1.12:/nfsroot /var/crash/
# kdumpctl restart
Rebuilt because "Detected change in File System"
# umount /var/crash/;kdumpctl restart
Rebuilt because "Detected change in File System"
Added "raw /dev/md0" in /etc/kdump.conf
# kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# mkfs.ext4 /dev/md0 ;kdumpctl restart
No rebuild
Added "ext4 /dev/md0" in /etc/kdump.conf
# mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
# umount /mnt;mkfs.ext4 /dev/md0;mount /dev/md0 /mnt
# mkdir /mnt/var;mkdir /mnt/var/crash; kdumpctl restart
Rebuilt because "Detected change in /etc/kdump.conf"
Most of the credits for this patch goes to Xunlei Pang <xpang@redhat.com>
for suggesting several improvements.
Signed-off-by: Pratyush Anand <panand@redhat.com>
Acked-by: Xunlei Pang <xlpang@redhat.com>
Acked-by: Baoquan He <xlpang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
2016-05-09 08:17:55 +00:00
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ]; then
|
|
|
|
return $ret
|
|
|
|
fi
|
|
|
|
|
2016-05-09 08:17:52 +00:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
check_rebuild()
|
2011-07-06 19:25:34 +00:00
|
|
|
{
|
2017-08-31 06:27:00 +00:00
|
|
|
local capture_capable_initrd="1"
|
2021-08-03 14:50:02 +00:00
|
|
|
local force_rebuild force_no_rebuild
|
2016-05-09 08:17:52 +00:00
|
|
|
local ret system_modified="0"
|
2012-06-14 01:57:27 +00:00
|
|
|
|
2016-11-03 18:46:31 +00:00
|
|
|
setup_initrd
|
2018-10-23 14:13:28 +00:00
|
|
|
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
if [ $? -ne 0 ]; then
|
|
|
|
return 1
|
|
|
|
fi
|
2011-07-06 19:25:34 +00:00
|
|
|
|
2021-08-03 14:50:02 +00:00
|
|
|
force_no_rebuild=$(kdump_get_conf_val force_no_rebuild)
|
|
|
|
force_no_rebuild=${force_no_rebuild:-0}
|
|
|
|
if [ "$force_no_rebuild" != "0" ] && [ "$force_no_rebuild" != "1" ];then
|
|
|
|
derror "Error: force_no_rebuild value is invalid"
|
|
|
|
return 1
|
2017-04-12 05:44:18 +00:00
|
|
|
fi
|
|
|
|
|
2021-08-03 14:50:02 +00:00
|
|
|
force_rebuild=$(kdump_get_conf_val force_rebuild)
|
|
|
|
force_rebuild=${force_rebuild:-0}
|
|
|
|
if [ "$force_rebuild" != "0" ] && [ "$force_rebuild" != "1" ];then
|
|
|
|
derror "Error: force_rebuild value is invalid"
|
|
|
|
return 1
|
2012-08-06 14:01:29 +00:00
|
|
|
fi
|
|
|
|
|
2017-04-12 05:44:18 +00:00
|
|
|
if [[ "$force_no_rebuild" == "1" && "$force_rebuild" == "1" ]]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Error: force_rebuild and force_no_rebuild are enabled simultaneously in kdump.conf"
|
2017-04-12 05:44:18 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
# Will not rebuild kdump initrd
|
|
|
|
if [ "$force_no_rebuild" == "1" ]; then
|
|
|
|
return 0
|
|
|
|
fi
|
|
|
|
|
2012-06-14 01:57:27 +00:00
|
|
|
#check to see if dependent files has been modified
|
|
|
|
#since last build of the image file
|
kdump: Rebuild default initrd for firmware assisted dump
The current kdump infrastructure builds a separate initrd which then
gets loaded into memory by kexec-tools for use by kdump kernel. But
firmware assisted dump (FADUMP) does not use kexec-based approach.
After crash, firmware reboots the partition and loads grub loader
like the normal booting process does. Hence in the FADUMP approach,
the second kernel (after crash) will always use the default initrd
(OS built). So, to support FADUMP, change is required, as in to add
dump capturing steps, in this initrd.
The current kdumpctl script implementation already has the code to
build initrd using mkdumprd. This patch uses the new '--rebuild'
option introduced, in dracut, to incrementally build the initramfs
image. Before rebuilding, we may need to probe the initrd image for
fadump support, to avoid rebuilding the initrd image multiple times
unnecessarily. This can be done using "lsinitrd" tool with the newly
proposed '--mod' option & inspecting the presence of "kdumpbase" in
the list of modules of default initrd image. We rebuild the image if
only "kdumpbase" module is missing in the initrd image. Also, before
rebuilding, a backup of default initrd image is taken.
Kexec-tools package in rhel7 is now enhanced to insert a out-of-tree
kdump module for dracut, which is responsible for adding vmcore
capture steps into initrd, if dracut is invoked with "IN_KDUMP"
environment variable set to 1. mkdumprd script exports "IN_KDUMP=1"
environment variable before invoking dracut to build kdump initrd.
This patch relies on this current mechanism of kdump init script.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
2014-07-24 18:39:07 +00:00
|
|
|
if [ -f $TARGET_INITRD ]; then
|
|
|
|
image_time=`stat -c "%Y" $TARGET_INITRD 2>/dev/null`
|
2017-08-31 06:27:00 +00:00
|
|
|
|
|
|
|
#in case of fadump mode, check whether the default/target
|
|
|
|
#initrd is already built with dump capture capability
|
|
|
|
if [ "$DEFAULT_DUMP_MODE" == "fadump" ]; then
|
2021-08-04 07:44:02 +00:00
|
|
|
capture_capable_initrd=$(lsinitrd -f $DRACUT_MODULES_FILE "$TARGET_INITRD" | grep -c -e ^kdumpbase$ -e ^zz-fadumpinit$)
|
2017-08-31 06:27:00 +00:00
|
|
|
fi
|
2011-07-06 19:25:34 +00:00
|
|
|
fi
|
|
|
|
|
2016-05-09 08:17:52 +00:00
|
|
|
check_system_modified
|
|
|
|
ret=$?
|
|
|
|
if [ $ret -eq 2 ]; then
|
|
|
|
return 1
|
|
|
|
elif [ $ret -eq 1 ];then
|
|
|
|
system_modified="1"
|
|
|
|
fi
|
|
|
|
|
2017-05-04 06:56:54 +00:00
|
|
|
if [ $image_time -eq 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "No kdump initial ramdisk found."
|
2017-08-31 06:27:00 +00:00
|
|
|
elif [ "$capture_capable_initrd" == "0" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Rebuild $TARGET_INITRD with dump capture support"
|
2012-08-06 14:01:29 +00:00
|
|
|
elif [ "$force_rebuild" != "0" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Force rebuild $TARGET_INITRD"
|
2016-05-09 08:17:52 +00:00
|
|
|
elif [ "$system_modified" != "0" ]; then
|
|
|
|
:
|
2012-06-14 01:57:27 +00:00
|
|
|
else
|
|
|
|
return 0
|
2011-07-06 19:25:34 +00:00
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Rebuilding $TARGET_INITRD"
|
2012-06-14 01:57:27 +00:00
|
|
|
rebuild_initrd
|
|
|
|
return $?
|
2011-07-06 19:25:34 +00:00
|
|
|
}
|
|
|
|
|
2021-02-18 06:01:18 +00:00
|
|
|
# On ppc64le LPARs, the keys trusted by firmware do not end up in
|
|
|
|
# .builtin_trusted_keys. So instead, add the key to the .ima keyring
|
|
|
|
function load_kdump_kernel_key()
|
|
|
|
{
|
|
|
|
# this is only called inside is_secure_boot_enforced,
|
|
|
|
# no need to retest
|
|
|
|
|
|
|
|
# this is only required if DT /ibm,secure-boot is a file.
|
|
|
|
# if it is a dir, we are on OpenPower and don't need this.
|
|
|
|
if ! [ -f /proc/device-tree/ibm,secure-boot ]; then
|
|
|
|
return
|
|
|
|
fi
|
|
|
|
|
2021-08-04 07:14:00 +00:00
|
|
|
KDUMP_KEY_ID=$(keyctl padd asymmetric kernelkey-$RANDOM %:.ima < "/usr/share/doc/kernel-keys/$KDUMP_KERNELVER/kernel-signing-ppc.cer")
|
2021-02-18 06:01:18 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
# remove a previously loaded key. There's no real security implication
|
|
|
|
# to leaving it around, we choose to do this because it makes it easier
|
|
|
|
# to be idempotent and so as to reduce the potential for confusion.
|
|
|
|
function remove_kdump_kernel_key()
|
|
|
|
{
|
|
|
|
if [ -z "$KDUMP_KEY_ID" ]; then
|
|
|
|
return
|
|
|
|
fi
|
|
|
|
|
|
|
|
keyctl unlink $KDUMP_KEY_ID %:.ima
|
|
|
|
}
|
|
|
|
|
2016-11-15 09:07:59 +00:00
|
|
|
# Load the kdump kernel specified in /etc/sysconfig/kdump
|
2011-07-06 19:25:34 +00:00
|
|
|
# If none is specified, try to load a kdump kernel with the same version
|
|
|
|
# as the currently running kernel.
|
2014-07-15 06:41:54 +00:00
|
|
|
load_kdump()
|
2011-07-06 19:25:34 +00:00
|
|
|
{
|
2020-10-27 09:04:24 +00:00
|
|
|
local ret
|
|
|
|
|
2018-05-22 10:15:07 +00:00
|
|
|
KEXEC_ARGS=$(prepare_kexec_args "${KEXEC_ARGS}")
|
|
|
|
KDUMP_COMMANDLINE=$(prepare_cmdline "${KDUMP_COMMANDLINE}" "${KDUMP_COMMANDLINE_REMOVE}" "${KDUMP_COMMANDLINE_APPEND}")
|
2011-07-06 19:25:34 +00:00
|
|
|
|
2020-06-29 13:13:54 +00:00
|
|
|
# For secureboot enabled machines, use new kexec file based syscall.
|
|
|
|
# Old syscall will always fail as it does not have capability to
|
|
|
|
# to kernel signature verification.
|
|
|
|
if is_secure_boot_enforced; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Secure Boot is enabled. Using kexec file based syscall."
|
2014-09-08 15:35:22 +00:00
|
|
|
KEXEC_ARGS="$KEXEC_ARGS -s"
|
2021-02-18 06:01:18 +00:00
|
|
|
load_kdump_kernel_key
|
2014-09-08 15:35:22 +00:00
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "$KEXEC $KEXEC_ARGS $standard_kexec_args --command-line=$KDUMP_COMMANDLINE --initrd=$TARGET_INITRD $KDUMP_KERNEL"
|
|
|
|
|
2020-10-29 02:21:09 +00:00
|
|
|
# The '12' represents an intermediate temporary file descriptor
|
|
|
|
# to store the standard error file descriptor '2', and later
|
|
|
|
# restore the error file descriptor with the file descriptor '12'
|
|
|
|
# and release it.
|
2020-10-27 09:04:24 +00:00
|
|
|
exec 12>&2
|
|
|
|
exec 2>> $KDUMP_LOG_PATH/kdump.log
|
|
|
|
PS4='+ $(date "+%Y-%m-%d %H:%M:%S") ${BASH_SOURCE}@${LINENO}: '
|
|
|
|
set -x
|
|
|
|
|
2011-07-06 19:25:34 +00:00
|
|
|
$KEXEC $KEXEC_ARGS $standard_kexec_args \
|
|
|
|
--command-line="$KDUMP_COMMANDLINE" \
|
2020-07-27 18:40:20 +00:00
|
|
|
--initrd=$TARGET_INITRD $KDUMP_KERNEL
|
2020-10-27 09:04:24 +00:00
|
|
|
|
|
|
|
ret=$?
|
|
|
|
set +x
|
|
|
|
exec 2>&12 12>&-
|
|
|
|
|
2021-02-18 06:01:18 +00:00
|
|
|
remove_kdump_kernel_key
|
|
|
|
|
2020-10-27 09:04:24 +00:00
|
|
|
if [ $ret == 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "kexec: loaded kdump kernel"
|
2011-07-06 19:25:34 +00:00
|
|
|
return 0
|
|
|
|
else
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "kexec: failed to load kdump kernel"
|
2011-07-06 19:25:34 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
check_ssh_config()
|
2012-02-22 03:16:09 +00:00
|
|
|
{
|
2017-05-11 05:44:28 +00:00
|
|
|
while read config_opt config_val; do
|
2012-02-22 03:16:09 +00:00
|
|
|
case "$config_opt" in
|
|
|
|
sshkey)
|
2017-05-11 05:44:29 +00:00
|
|
|
# remove inline comments after the end of a directive.
|
2012-02-22 03:16:09 +00:00
|
|
|
if [ -f "$config_val" ]; then
|
|
|
|
# canonicalize the path
|
|
|
|
SSH_KEY_LOCATION=$(/usr/bin/readlink -m $config_val)
|
|
|
|
else
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "WARNING: '$config_val' doesn't exist, using default value '$SSH_KEY_LOCATION'"
|
2012-02-22 03:16:09 +00:00
|
|
|
fi
|
|
|
|
;;
|
|
|
|
path)
|
|
|
|
SAVE_PATH=$config_val
|
|
|
|
;;
|
2012-07-23 07:31:28 +00:00
|
|
|
ssh)
|
2012-02-22 03:16:09 +00:00
|
|
|
DUMP_TARGET=$config_val
|
|
|
|
;;
|
|
|
|
*)
|
|
|
|
;;
|
|
|
|
esac
|
2021-08-03 11:49:51 +00:00
|
|
|
done <<< "$(kdump_read_conf)"
|
2012-02-22 03:16:09 +00:00
|
|
|
|
|
|
|
#make sure they've configured kdump.conf for ssh dumps
|
2012-03-28 08:23:38 +00:00
|
|
|
local SSH_TARGET=`echo -n $DUMP_TARGET | sed -n '/.*@/p'`
|
2012-02-22 03:16:09 +00:00
|
|
|
if [ -z "$SSH_TARGET" ]; then
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2019-08-12 08:07:39 +00:00
|
|
|
# ipv6 host address may takes a long time to be ready.
|
|
|
|
# Instead of checking against ipv6 address, we just check the network reachable
|
|
|
|
# by the return val of 'ssh'
|
|
|
|
check_and_wait_network_ready()
|
|
|
|
{
|
|
|
|
local start_time=$(date +%s)
|
2019-09-24 03:19:12 +00:00
|
|
|
local warn_once=1
|
2019-08-12 08:07:39 +00:00
|
|
|
local cur
|
|
|
|
local diff
|
2019-08-28 07:22:22 +00:00
|
|
|
local retval
|
|
|
|
local errmsg
|
2019-08-12 08:07:39 +00:00
|
|
|
|
|
|
|
while true; do
|
2019-08-28 07:22:22 +00:00
|
|
|
errmsg=$(ssh -i $SSH_KEY_LOCATION -o BatchMode=yes $DUMP_TARGET mkdir -p $SAVE_PATH 2>&1)
|
|
|
|
retval=$?
|
|
|
|
|
2019-08-12 08:07:39 +00:00
|
|
|
# ssh exits with the exit status of the remote command or with 255 if an error occurred
|
2019-08-28 07:22:22 +00:00
|
|
|
if [ $retval -eq 0 ]; then
|
2019-08-12 08:07:39 +00:00
|
|
|
return 0
|
2019-08-28 07:22:22 +00:00
|
|
|
elif [ $retval -ne 255 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Could not create $DUMP_TARGET:$SAVE_PATH, you should check the privilege on server side"
|
2019-08-12 08:07:39 +00:00
|
|
|
return 1
|
|
|
|
fi
|
2019-08-28 07:22:22 +00:00
|
|
|
|
|
|
|
# if server removes the authorized_keys or, no /root/.ssh/kdump_id_rsa
|
2020-10-27 09:04:22 +00:00
|
|
|
ddebug "$errmsg"
|
2021-08-04 07:44:02 +00:00
|
|
|
echo $errmsg | grep -q "Permission denied\|No such file or directory\|Host key verification failed"
|
2019-08-28 07:22:22 +00:00
|
|
|
if [ $? -eq 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Could not create $DUMP_TARGET:$SAVE_PATH, you probably need to run \"kdumpctl propagate\""
|
2019-08-28 07:22:22 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2019-09-24 03:19:12 +00:00
|
|
|
if [ $warn_once -eq 1 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "Network dump target is not usable, waiting for it to be ready..."
|
2019-09-24 03:19:12 +00:00
|
|
|
warn_once=0
|
|
|
|
fi
|
|
|
|
|
2019-08-12 08:07:39 +00:00
|
|
|
cur=$(date +%s)
|
2021-08-04 07:18:59 +00:00
|
|
|
diff=$((cur - start_time))
|
2019-08-12 08:07:39 +00:00
|
|
|
# 60s time out
|
2019-08-28 07:22:22 +00:00
|
|
|
if [ $diff -gt 180 ]; then
|
2019-08-12 08:07:39 +00:00
|
|
|
break;
|
|
|
|
fi
|
|
|
|
sleep 1
|
|
|
|
done
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Could not create $DUMP_TARGET:$SAVE_PATH, ipaddr is not ready yet. You should check network connection"
|
2019-08-12 08:07:39 +00:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
check_ssh_target()
|
2012-02-22 03:16:09 +00:00
|
|
|
{
|
2019-08-12 08:07:39 +00:00
|
|
|
check_and_wait_network_ready
|
|
|
|
if [ $? -ne 0 ]; then
|
2013-02-18 09:05:43 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
return 0
|
2012-02-22 03:16:09 +00:00
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
propagate_ssh_key()
|
2011-07-06 19:25:34 +00:00
|
|
|
{
|
2012-02-22 03:16:09 +00:00
|
|
|
check_ssh_config
|
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "No ssh config specified in $KDUMP_CONFIG_FILE. Can't propagate"
|
2012-02-22 03:16:09 +00:00
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
local KEYFILE=$SSH_KEY_LOCATION
|
2011-07-06 19:25:34 +00:00
|
|
|
local errmsg="Failed to propagate ssh key"
|
|
|
|
|
|
|
|
#Check to see if we already created key, if not, create it.
|
|
|
|
if [ -f $KEYFILE ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Using existing keys..."
|
2011-07-06 19:25:34 +00:00
|
|
|
else
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Generating new ssh keys... "
|
2012-02-22 03:16:09 +00:00
|
|
|
/usr/bin/ssh-keygen -t rsa -f $KEYFILE -N "" 2>&1 > /dev/null
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "done."
|
2011-07-06 19:25:34 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
#now find the target ssh user and server to contact.
|
2012-02-22 03:16:09 +00:00
|
|
|
SSH_USER=`echo $DUMP_TARGET | cut -d\ -f2 | cut -d@ -f1`
|
|
|
|
SSH_SERVER=`echo $DUMP_TARGET | sed -e's/\(.*@\)\(.*$\)/\2/'`
|
2014-07-15 06:41:54 +00:00
|
|
|
|
2011-07-06 19:25:34 +00:00
|
|
|
#now send the found key to the found server
|
2012-02-22 03:16:09 +00:00
|
|
|
ssh-copy-id -i $KEYFILE $SSH_USER@$SSH_SERVER
|
2011-07-06 19:25:34 +00:00
|
|
|
RET=$?
|
|
|
|
if [ $RET == 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "$KEYFILE has been added to ~$SSH_USER/.ssh/authorized_keys on $SSH_SERVER"
|
2011-07-06 19:25:34 +00:00
|
|
|
return 0
|
|
|
|
else
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "$errmsg, $KEYFILE failed in transfer to $SSH_SERVER"
|
2011-07-06 19:25:34 +00:00
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
2018-05-11 02:02:39 +00:00
|
|
|
show_reserved_mem()
|
|
|
|
{
|
2021-08-04 07:14:00 +00:00
|
|
|
local mem
|
|
|
|
local mem_mb
|
|
|
|
|
|
|
|
mem=$(</sys/kernel/kexec_crash_size)
|
2021-08-04 07:18:59 +00:00
|
|
|
mem_mb=$((mem / 1024 / 1024))
|
2018-05-11 02:02:39 +00:00
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Reserved "$mem_mb"MB memory for crash kernel"
|
2018-05-11 02:02:39 +00:00
|
|
|
}
|
|
|
|
|
2014-07-24 18:38:36 +00:00
|
|
|
check_current_fadump_status()
|
|
|
|
{
|
|
|
|
# Check if firmware-assisted dump has been registered.
|
2021-08-04 07:14:00 +00:00
|
|
|
rc=$(<$FADUMP_REGISTER_SYS_NODE)
|
|
|
|
[[ $rc -eq 1 ]] && return 0
|
2014-07-24 18:38:36 +00:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
|
|
|
check_current_status()
|
|
|
|
{
|
|
|
|
if [ $DEFAULT_DUMP_MODE == "fadump" ]; then
|
|
|
|
check_current_fadump_status
|
|
|
|
else
|
|
|
|
check_current_kdump_status
|
|
|
|
fi
|
|
|
|
|
|
|
|
return $?
|
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
save_raw()
|
2012-04-28 10:01:18 +00:00
|
|
|
{
|
|
|
|
local kdump_dir
|
|
|
|
local raw_target
|
|
|
|
|
2021-08-03 14:50:02 +00:00
|
|
|
raw_target=$(kdump_get_conf_val raw)
|
2012-04-28 10:01:18 +00:00
|
|
|
[ -z "$raw_target" ] && return 0
|
|
|
|
[ -b "$raw_target" ] || {
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "raw partition $raw_target not found"
|
2012-04-28 10:01:18 +00:00
|
|
|
return 1
|
|
|
|
}
|
2018-08-15 13:14:15 +00:00
|
|
|
check_fs=$(lsblk --nodeps -npo FSTYPE $raw_target)
|
|
|
|
if [[ $(echo $check_fs | wc -w) -ne 0 ]]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "Warning: Detected '$check_fs' signature on $raw_target, data loss is expected."
|
2018-08-15 13:14:15 +00:00
|
|
|
return 0
|
|
|
|
fi
|
2021-08-03 14:50:02 +00:00
|
|
|
kdump_dir=$(kdump_get_conf_val path)
|
2012-04-28 10:01:18 +00:00
|
|
|
if [ -z "${kdump_dir}" ]; then
|
|
|
|
coredir="/var/crash/`date +"%Y-%m-%d-%H:%M"`"
|
|
|
|
else
|
|
|
|
coredir="${kdump_dir}/`date +"%Y-%m-%d-%H:%M"`"
|
|
|
|
fi
|
|
|
|
|
|
|
|
mkdir -p "$coredir"
|
|
|
|
[ -d "$coredir" ] || {
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "failed to create $coredir"
|
2012-04-28 10:01:18 +00:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
if makedumpfile -R $coredir/vmcore <$raw_target >/dev/null 2>&1; then
|
|
|
|
# dump found
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Dump saved to $coredir/vmcore"
|
2012-04-28 10:01:18 +00:00
|
|
|
# wipe makedumpfile header
|
|
|
|
dd if=/dev/zero of=$raw_target bs=1b count=1 2>/dev/null
|
|
|
|
else
|
|
|
|
rm -rf "$coredir"
|
|
|
|
fi
|
|
|
|
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2013-06-08 06:22:31 +00:00
|
|
|
local_fs_dump_target()
|
|
|
|
{
|
|
|
|
local _target
|
|
|
|
|
2021-08-04 07:44:02 +00:00
|
|
|
_target=$(grep -E "^ext[234]|^xfs|^btrfs|^minix" /etc/kdump.conf)
|
2013-06-08 06:22:31 +00:00
|
|
|
if [ $? -eq 0 ]; then
|
|
|
|
echo $_target|awk '{print $2}'
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
path_to_be_relabeled()
|
|
|
|
{
|
2013-06-08 06:22:31 +00:00
|
|
|
local _path _target _mnt="/" _rmnt
|
|
|
|
|
2020-03-05 07:34:06 +00:00
|
|
|
if is_user_configured_dump_target; then
|
|
|
|
if is_mount_in_dracut_args; then
|
|
|
|
return;
|
|
|
|
fi
|
|
|
|
|
2013-06-08 06:22:31 +00:00
|
|
|
_target=$(local_fs_dump_target)
|
|
|
|
if [[ -n "$_target" ]]; then
|
2020-03-12 12:57:08 +00:00
|
|
|
_mnt=$(get_mntpoint_from_target $_target)
|
|
|
|
if ! is_mounted "$_mnt"; then
|
2013-06-08 06:22:31 +00:00
|
|
|
return
|
|
|
|
fi
|
|
|
|
else
|
|
|
|
return
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
|
|
|
_path=$(get_save_path)
|
|
|
|
# if $_path is masked by other mount, we will not relabel it.
|
|
|
|
_rmnt=$(df $_mnt/$_path 2>/dev/null | tail -1 | awk '{ print $NF }')
|
|
|
|
if [ "$_rmnt" == "$_mnt" ]; then
|
|
|
|
echo $_mnt/$_path
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
|
|
|
selinux_relabel()
|
|
|
|
{
|
|
|
|
local _path _i _attr
|
|
|
|
|
|
|
|
_path=$(path_to_be_relabeled)
|
|
|
|
if [ -z "$_path" ] || ! [ -d "$_path" ] ; then
|
|
|
|
return
|
|
|
|
fi
|
|
|
|
|
2021-08-04 08:22:17 +00:00
|
|
|
while IFS= read -r -d '' _i; do
|
|
|
|
_attr=$(getfattr -m "security.selinux" "$_i" 2>/dev/null)
|
2013-06-08 06:22:31 +00:00
|
|
|
if [ -z "$_attr" ]; then
|
2021-08-04 08:22:17 +00:00
|
|
|
restorecon "$_i";
|
2013-06-08 06:22:31 +00:00
|
|
|
fi
|
2021-08-04 08:22:17 +00:00
|
|
|
done < <(find "$_path" -print0)
|
2013-06-08 06:22:31 +00:00
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
check_fence_kdump_config()
|
2014-04-02 08:33:47 +00:00
|
|
|
{
|
|
|
|
local hostname=`hostname`
|
2017-05-17 03:16:22 +00:00
|
|
|
local ipaddrs=`hostname -I`
|
kdump-lib.sh: add a config value retrive helper
Add a helper kdump_get_conf_val to replace get_option_value.
It can help cover more corner cases in the code, like when there are
multiple spaces in config file, config value separated by a tab,
heading spaces, or trailing comments.
And this uses "sed group command" and "sed hold buffer", make it much
faster than previous `grep <config> | tail -1`.
This helper is supposed to provide a universal way for kexec-tools
scripts to read in config value. Currently, different scripts are
reading the config in many different fragile ways.
For example, following codes are found in kexec-tools script code base:
1. grep ^force_rebuild $KDUMP_CONFIG_FILE
echo $_force_rebuild | cut -d' ' -f2
2. grep ^kdump_post $KDUMP_CONFIG_FILE | cut -d\ -f2
3. awk '/^sshkey/ {print $2}' $conf_file
4. grep ^path $KDUMP_CONFIG_FILE | cut -d' ' -f2-
1, 2, and 4 will fail if the space is replaced by, e.g. a tab
1 and 2 might fail if there are multiple spaces between config name
and config value:
"kdump_post /var/crash/scripts/kdump-post.sh"
A space will be read instead of config value.
1, 2, 3 will fail if there are space in file path, like:
"kdump_post /var/crash/scripts dir/kdump-post.sh"
4 will fail if there are trailing comments:
"path /var/crash # some comment here"
And all will fail if there are heading space,
" path /var/crash"
And all will most likely cause problems if the config file contains
the same option more than once.
And all of them are slower than the new sed call. Old get_option_value
is also very slow and doesn't handle heading space.
Although we never claim to support heading space or tailing comments
before, it's harmless to be more robust on config reading, and many
conf files in /etc support heading spaces. And have a faster and
safer config reading helper makes it easier to clean up the code.
Signed-off-by: Kairui Song <kasong@redhat.com>
Acked-by: Philipp Rudo <prudo@redhat.com>
2021-08-16 15:25:14 +00:00
|
|
|
local nodes=$(kdump_get_conf_val "fence_kdump_nodes")
|
2014-04-02 08:33:47 +00:00
|
|
|
|
|
|
|
for node in $nodes; do
|
|
|
|
if [ "$node" = "$hostname" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Option fence_kdump_nodes cannot contain $hostname"
|
2014-04-02 08:33:47 +00:00
|
|
|
return 1
|
|
|
|
fi
|
2017-05-17 03:16:22 +00:00
|
|
|
# node can be ipaddr
|
2021-08-04 07:44:02 +00:00
|
|
|
echo "$ipaddrs " | grep -q "$node "
|
2017-05-17 03:16:22 +00:00
|
|
|
if [ $? -eq 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Option fence_kdump_nodes cannot contain $node"
|
2017-05-17 03:16:22 +00:00
|
|
|
return 1
|
|
|
|
fi
|
2014-04-02 08:33:47 +00:00
|
|
|
done
|
|
|
|
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2014-07-24 18:38:36 +00:00
|
|
|
check_dump_feasibility()
|
|
|
|
{
|
|
|
|
if [ $DEFAULT_DUMP_MODE == "fadump" ]; then
|
|
|
|
return 0
|
|
|
|
fi
|
|
|
|
|
|
|
|
check_kdump_feasibility
|
|
|
|
return $?
|
|
|
|
}
|
|
|
|
|
2014-07-24 18:38:53 +00:00
|
|
|
start_fadump()
|
|
|
|
{
|
|
|
|
echo 1 > $FADUMP_REGISTER_SYS_NODE
|
|
|
|
if ! check_current_fadump_status; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "fadump: failed to register"
|
2014-07-24 18:38:53 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "fadump: registered successfully"
|
2014-07-24 18:38:53 +00:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
start_dump()
|
|
|
|
{
|
|
|
|
if [ $DEFAULT_DUMP_MODE == "fadump" ]; then
|
|
|
|
start_fadump
|
|
|
|
else
|
|
|
|
load_kdump
|
|
|
|
fi
|
|
|
|
|
|
|
|
return $?
|
|
|
|
}
|
|
|
|
|
2019-01-17 20:31:23 +00:00
|
|
|
check_failure_action_config()
|
2015-06-11 08:22:11 +00:00
|
|
|
{
|
|
|
|
local default_option
|
2019-01-17 20:31:23 +00:00
|
|
|
local failure_action
|
|
|
|
local option="failure_action"
|
2015-06-11 08:22:11 +00:00
|
|
|
|
2021-08-03 14:50:02 +00:00
|
|
|
default_option=$(kdump_get_conf_val default)
|
|
|
|
failure_action=$(kdump_get_conf_val failure_action)
|
2019-01-17 20:31:23 +00:00
|
|
|
|
|
|
|
if [ -z "$failure_action" -a -z "$default_option" ]; then
|
2015-06-11 08:22:11 +00:00
|
|
|
return 0
|
2019-01-17 20:31:23 +00:00
|
|
|
elif [ -n "$failure_action" -a -n "$default_option" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Cannot specify 'failure_action' and 'default' option together"
|
2019-01-17 20:31:23 +00:00
|
|
|
return 1
|
2015-06-11 08:22:11 +00:00
|
|
|
fi
|
2019-01-17 20:31:23 +00:00
|
|
|
|
|
|
|
if [ -n "$default_option" ]; then
|
|
|
|
option="default"
|
|
|
|
failure_action="$default_option"
|
|
|
|
fi
|
|
|
|
|
|
|
|
case "$failure_action" in
|
|
|
|
reboot|halt|poweroff|shell|dump_to_rootfs)
|
|
|
|
return 0
|
|
|
|
;;
|
|
|
|
*)
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo $"Usage kdump.conf: $option {reboot|halt|poweroff|shell|dump_to_rootfs}"
|
2019-01-17 20:31:23 +00:00
|
|
|
return 1
|
|
|
|
esac
|
2015-06-11 08:22:11 +00:00
|
|
|
}
|
|
|
|
|
2019-01-17 20:31:24 +00:00
|
|
|
check_final_action_config()
|
|
|
|
{
|
|
|
|
local final_action
|
|
|
|
|
2021-08-03 14:50:02 +00:00
|
|
|
final_action=$(kdump_get_conf_val final_action)
|
2019-01-17 20:31:24 +00:00
|
|
|
if [ -z "$final_action" ]; then
|
|
|
|
return 0
|
|
|
|
else
|
|
|
|
case "$final_action" in
|
|
|
|
reboot|halt|poweroff)
|
|
|
|
return 0
|
|
|
|
;;
|
|
|
|
*)
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo $"Usage kdump.conf: final_action {reboot|halt|poweroff}"
|
2019-01-17 20:31:24 +00:00
|
|
|
return 1
|
|
|
|
esac
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
2014-07-15 06:41:54 +00:00
|
|
|
start()
|
2011-07-06 19:25:34 +00:00
|
|
|
{
|
2017-04-29 01:15:00 +00:00
|
|
|
check_dump_feasibility
|
2013-03-11 09:31:25 +00:00
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Starting kdump: [FAILED]"
|
2012-04-28 07:17:13 +00:00
|
|
|
return 1
|
2013-03-11 09:31:25 +00:00
|
|
|
fi
|
2012-04-28 07:17:13 +00:00
|
|
|
|
2017-04-29 01:15:00 +00:00
|
|
|
check_config
|
2012-04-28 10:01:18 +00:00
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Starting kdump: [FAILED]"
|
2012-04-28 10:01:18 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2017-04-29 01:15:00 +00:00
|
|
|
if sestatus 2>/dev/null | grep -q "SELinux status.*enabled"; then
|
|
|
|
selinux_relabel
|
|
|
|
fi
|
|
|
|
|
|
|
|
save_raw
|
2014-02-12 02:31:41 +00:00
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Starting kdump: [FAILED]"
|
2014-02-12 02:31:41 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2014-07-24 18:38:36 +00:00
|
|
|
check_current_status
|
2014-02-13 03:23:58 +00:00
|
|
|
if [ $? == 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "Kdump already running: [WARNING]"
|
2014-02-13 03:23:58 +00:00
|
|
|
return 0
|
2011-07-06 19:25:34 +00:00
|
|
|
fi
|
2012-02-22 03:16:09 +00:00
|
|
|
|
2013-02-18 09:05:43 +00:00
|
|
|
if check_ssh_config; then
|
|
|
|
if ! check_ssh_target; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Starting kdump: [FAILED]"
|
2013-02-18 09:05:43 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
2013-03-05 08:07:37 +00:00
|
|
|
check_rebuild
|
2011-07-06 19:25:34 +00:00
|
|
|
if [ $? != 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Starting kdump: [FAILED]"
|
2011-07-06 19:25:34 +00:00
|
|
|
return 1
|
|
|
|
fi
|
2014-07-24 18:38:53 +00:00
|
|
|
|
|
|
|
start_dump
|
2011-07-06 19:25:34 +00:00
|
|
|
if [ $? != 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Starting kdump: [FAILED]"
|
2011-07-06 19:25:34 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Starting kdump: [OK]"
|
2011-07-06 19:25:34 +00:00
|
|
|
}
|
|
|
|
|
2018-10-23 14:13:28 +00:00
|
|
|
reload()
|
|
|
|
{
|
|
|
|
check_current_status
|
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dwarn "Kdump was not running: [WARNING]"
|
2018-10-23 14:13:28 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
if [ $DEFAULT_DUMP_MODE == "fadump" ]; then
|
2019-02-28 04:50:29 +00:00
|
|
|
reload_fadump
|
|
|
|
return $?
|
2018-10-23 14:13:28 +00:00
|
|
|
else
|
|
|
|
stop_kdump
|
|
|
|
fi
|
|
|
|
|
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Stopping kdump: [FAILED]"
|
2018-10-23 14:13:28 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Stopping kdump: [OK]"
|
2018-10-23 14:13:28 +00:00
|
|
|
|
|
|
|
setup_initrd
|
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Starting kdump: [FAILED]"
|
2018-10-23 14:13:28 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
start_dump
|
|
|
|
if [ $? -ne 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Starting kdump: [FAILED]"
|
2018-10-23 14:13:28 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Starting kdump: [OK]"
|
2018-10-23 14:13:28 +00:00
|
|
|
}
|
|
|
|
|
2014-07-24 18:39:00 +00:00
|
|
|
stop_fadump()
|
|
|
|
{
|
|
|
|
echo 0 > $FADUMP_REGISTER_SYS_NODE
|
|
|
|
if check_current_fadump_status; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "fadump: failed to unregister"
|
2014-07-24 18:39:00 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "fadump: unregistered successfully"
|
2014-07-24 18:39:00 +00:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
stop_kdump()
|
2011-07-06 19:25:34 +00:00
|
|
|
{
|
2020-06-29 13:13:54 +00:00
|
|
|
if is_secure_boot_enforced; then
|
2014-09-08 15:35:21 +00:00
|
|
|
$KEXEC -s -p -u
|
|
|
|
else
|
|
|
|
$KEXEC -p -u
|
|
|
|
fi
|
|
|
|
|
2014-07-24 18:39:00 +00:00
|
|
|
if [ $? != 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "kexec: failed to unload kdump kernel"
|
2014-07-24 18:39:00 +00:00
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "kexec: unloaded kdump kernel"
|
2014-07-24 18:39:00 +00:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2019-02-28 04:50:29 +00:00
|
|
|
reload_fadump()
|
|
|
|
{
|
|
|
|
echo 1 > $FADUMP_REGISTER_SYS_NODE
|
|
|
|
if [ $? == 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "fadump: re-registered successfully"
|
2019-02-28 04:50:29 +00:00
|
|
|
return 0
|
|
|
|
else
|
|
|
|
# FADump could fail on older kernel where re-register
|
|
|
|
# support is not enabled. Try stop/start from userspace
|
|
|
|
# to handle such scenario.
|
|
|
|
stop_fadump
|
|
|
|
if [ $? == 0 ]; then
|
|
|
|
start_fadump
|
|
|
|
return $?
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2014-07-24 18:39:00 +00:00
|
|
|
stop()
|
|
|
|
{
|
|
|
|
if [ $DEFAULT_DUMP_MODE == "fadump" ]; then
|
|
|
|
stop_fadump
|
|
|
|
else
|
|
|
|
stop_kdump
|
|
|
|
fi
|
|
|
|
|
|
|
|
if [ $? != 0 ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Stopping kdump: [FAILED]"
|
2011-07-06 19:25:34 +00:00
|
|
|
return 1
|
|
|
|
fi
|
2014-07-24 18:39:00 +00:00
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Stopping kdump: [OK]"
|
2014-07-24 18:39:00 +00:00
|
|
|
return 0
|
2011-07-06 19:25:34 +00:00
|
|
|
}
|
|
|
|
|
2019-03-29 03:29:30 +00:00
|
|
|
rebuild() {
|
2019-05-23 09:34:05 +00:00
|
|
|
check_config
|
|
|
|
if [ $? -ne 0 ]; then
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2019-05-27 06:46:49 +00:00
|
|
|
if check_ssh_config; then
|
|
|
|
if ! check_ssh_target; then
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
2019-03-29 03:29:30 +00:00
|
|
|
setup_initrd
|
|
|
|
if [ $? -ne 0 ]; then
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Rebuilding $TARGET_INITRD"
|
2019-03-29 03:29:30 +00:00
|
|
|
rebuild_initrd
|
|
|
|
return $?
|
|
|
|
}
|
|
|
|
|
2021-04-21 19:27:10 +00:00
|
|
|
do_estimate() {
|
|
|
|
local kdump_mods
|
|
|
|
local -A large_mods
|
|
|
|
local baseline
|
2021-07-14 19:08:28 +00:00
|
|
|
local kernel_size mod_size initrd_size baseline_size runtime_size reserved_size estimated_size recommended_size
|
2021-04-21 19:27:10 +00:00
|
|
|
local size_mb=$(( 1024 * 1024 ))
|
|
|
|
|
|
|
|
setup_initrd
|
|
|
|
if [ ! -f "$TARGET_INITRD" ]; then
|
|
|
|
derror "kdumpctl estimate: kdump initramfs is not built yet."
|
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
kdump_mods="$(lsinitrd "$TARGET_INITRD" -f /usr/lib/dracut/hostonly-kernel-modules.txt | tr '\n' ' ')"
|
|
|
|
baseline=$(kdump_get_arch_recommend_size)
|
|
|
|
if [[ "${baseline: -1}" == "M" ]]; then
|
|
|
|
baseline=${baseline%M}
|
|
|
|
elif [[ "${baseline: -1}" == "G" ]]; then
|
|
|
|
baseline=$(( ${baseline%G} * 1024 ))
|
|
|
|
elif [[ "${baseline: -1}" == "T" ]]; then
|
|
|
|
baseline=$(( ${baseline%Y} * 1048576 ))
|
|
|
|
fi
|
|
|
|
|
2021-07-30 06:40:45 +00:00
|
|
|
# The default pre-reserved crashkernel value
|
2021-04-21 19:27:10 +00:00
|
|
|
baseline_size=$((baseline * size_mb))
|
|
|
|
# Current reserved crashkernel size
|
2021-08-04 07:14:00 +00:00
|
|
|
reserved_size=$(</sys/kernel/kexec_crash_size)
|
2021-04-21 19:27:10 +00:00
|
|
|
# A pre-estimated value for userspace usage and kernel
|
|
|
|
# runtime allocation, 64M should good for most cases
|
|
|
|
runtime_size=$((64 * size_mb))
|
|
|
|
# Kernel image size
|
|
|
|
kernel_size=$(get_kernel_size "$KDUMP_KERNEL")
|
|
|
|
# Kdump initramfs size
|
|
|
|
initrd_size=$(du -b "$TARGET_INITRD" | awk '{print $1}')
|
|
|
|
# Kernel modules static size after loaded
|
|
|
|
mod_size=0
|
|
|
|
while read -r _name _size _; do
|
|
|
|
if [[ ! " $kdump_mods " == *" $_name "* ]]; then
|
|
|
|
continue
|
|
|
|
fi
|
|
|
|
mod_size=$((mod_size + _size))
|
|
|
|
|
|
|
|
# Mark module with static size larger than 2M as large module
|
|
|
|
if [[ $((_size / size_mb)) -ge 1 ]]; then
|
|
|
|
large_mods[$_name]=$_size
|
|
|
|
fi
|
|
|
|
done <<< "$(< /proc/modules)"
|
|
|
|
|
|
|
|
# Extra memory usage required for LUKS2 decryption
|
|
|
|
crypt_size=0
|
|
|
|
for _dev in $(get_all_kdump_crypt_dev); do
|
|
|
|
_crypt_info=$(cryptsetup luksDump "/dev/block/$_dev")
|
|
|
|
[[ $(echo "$_crypt_info" | sed -n "s/^Version:\s*\(.*\)/\1/p" ) == "2" ]] || continue
|
|
|
|
for _mem in $(echo "$_crypt_info" | sed -n "s/\sMemory:\s*\(.*\)/\1/p" | sort -n ); do
|
|
|
|
crypt_size=$((crypt_size + _mem * 1024))
|
|
|
|
break
|
|
|
|
done
|
|
|
|
done
|
|
|
|
[[ $crypt_size -ne 0 ]] && echo -e "Encrypted kdump target requires extra memory, assuming using the keyslot with minimun memory requirement\n"
|
|
|
|
|
|
|
|
estimated_size=$((kernel_size + mod_size + initrd_size + runtime_size + crypt_size))
|
|
|
|
if [[ $baseline_size -gt $estimated_size ]]; then
|
2021-07-14 19:08:28 +00:00
|
|
|
recommended_size=$baseline_size
|
2021-04-21 19:27:10 +00:00
|
|
|
else
|
2021-07-14 19:08:28 +00:00
|
|
|
recommended_size=$estimated_size
|
2021-04-21 19:27:10 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
echo "Reserved crashkernel: $((reserved_size / size_mb))M"
|
2021-07-14 19:08:28 +00:00
|
|
|
echo "Recommended crashkernel: $((recommended_size / size_mb))M"
|
2021-04-21 19:27:10 +00:00
|
|
|
echo
|
|
|
|
echo "Kernel image size: $((kernel_size / size_mb))M"
|
|
|
|
echo "Kernel modules size: $((mod_size / size_mb))M"
|
|
|
|
echo "Initramfs size: $((initrd_size / size_mb))M"
|
|
|
|
echo "Runtime reservation: $((runtime_size / size_mb))M"
|
|
|
|
[[ $crypt_size -ne 0 ]] && \
|
|
|
|
echo "LUKS required size: $((crypt_size / size_mb))M"
|
|
|
|
echo -n "Large modules:"
|
|
|
|
if [[ "${#large_mods[@]}" -eq 0 ]]; then
|
|
|
|
echo " <none>"
|
|
|
|
else
|
|
|
|
echo ""
|
|
|
|
for _mod in "${!large_mods[@]}"; do
|
|
|
|
echo " $_mod: ${large_mods[$_mod]}"
|
|
|
|
done
|
|
|
|
fi
|
|
|
|
|
2021-07-14 19:08:28 +00:00
|
|
|
if [[ $reserved_size -le $recommended_size ]]; then
|
|
|
|
echo "WARNING: Current crashkernel size is lower than recommended size $((recommended_size / size_mb))M."
|
2021-04-21 19:27:10 +00:00
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
2021-06-10 05:06:22 +00:00
|
|
|
reset_crashkernel() {
|
|
|
|
local kernel=$1 entry crashkernel_default
|
|
|
|
local grub_etc_default="/etc/default/grub"
|
|
|
|
|
|
|
|
[[ -z "$kernel" ]] && kernel=$(uname -r)
|
|
|
|
crashkernel_default=$(cat "/usr/lib/modules/$kernel/crashkernel.default" 2>/dev/null)
|
|
|
|
|
|
|
|
if [[ -z "$crashkernel_default" ]]; then
|
|
|
|
derror "$kernel doesn't have a crashkernel.default"
|
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
if is_atomic; then
|
|
|
|
if rpm-ostree kargs | grep -q "crashkernel="; then
|
|
|
|
rpm-ostree --replace="crashkernel=$crashkernel_default"
|
|
|
|
else
|
|
|
|
rpm-ostree --append="crashkernel=$crashkernel_default"
|
|
|
|
fi
|
|
|
|
else
|
|
|
|
entry=$(grubby --info ALL | grep "^kernel=.*$kernel")
|
|
|
|
entry=${entry#kernel=}
|
|
|
|
entry=${entry#\"}
|
|
|
|
entry=${entry%\"}
|
|
|
|
|
|
|
|
if [[ -f "$grub_etc_default" ]]; then
|
|
|
|
sed -i -e "s/^\(GRUB_CMDLINE_LINUX=.*\)crashkernel=[^\ \"]*\([\ \"].*\)$/\1$crashkernel_default\2/" "$grub_etc_default"
|
|
|
|
fi
|
|
|
|
|
|
|
|
[[ -f /etc/zipl.conf ]] && zipl_arg="--zipl"
|
|
|
|
grubby --args "$crashkernel_default" --update-kernel "$entry" $zipl_arg
|
|
|
|
[[ $zipl_arg ]] && zipl > /dev/null
|
|
|
|
fi
|
2021-08-03 11:49:51 +00:00
|
|
|
}
|
2021-06-10 05:06:22 +00:00
|
|
|
|
2012-04-28 10:01:18 +00:00
|
|
|
if [ ! -f "$KDUMP_CONFIG_FILE" ]; then
|
2020-10-27 09:04:22 +00:00
|
|
|
derror "Error: No kdump config file found!"
|
2012-04-28 10:01:18 +00:00
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
|
2013-11-25 16:23:11 +00:00
|
|
|
main ()
|
|
|
|
{
|
2014-07-24 18:38:36 +00:00
|
|
|
# Determine if the dump mode is kdump or fadump
|
|
|
|
determine_dump_mode
|
|
|
|
|
2013-11-25 16:23:11 +00:00
|
|
|
case "$1" in
|
|
|
|
start)
|
|
|
|
if [ -s /proc/vmcore ]; then
|
|
|
|
save_core
|
|
|
|
reboot
|
|
|
|
else
|
|
|
|
start
|
|
|
|
fi
|
|
|
|
;;
|
|
|
|
stop)
|
|
|
|
stop
|
|
|
|
;;
|
|
|
|
status)
|
2011-07-06 19:25:34 +00:00
|
|
|
EXIT_CODE=0
|
2014-07-24 18:38:36 +00:00
|
|
|
check_current_status
|
2013-11-25 16:23:11 +00:00
|
|
|
case "$?" in
|
|
|
|
0)
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Kdump is operational"
|
2013-11-25 16:23:11 +00:00
|
|
|
EXIT_CODE=0
|
|
|
|
;;
|
|
|
|
1)
|
2020-10-27 09:04:22 +00:00
|
|
|
dinfo "Kdump is not operational"
|
2013-11-25 16:23:11 +00:00
|
|
|
EXIT_CODE=3
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
exit $EXIT_CODE
|
2011-07-06 19:25:34 +00:00
|
|
|
;;
|
2018-10-23 14:13:28 +00:00
|
|
|
reload)
|
|
|
|
reload
|
|
|
|
;;
|
2013-11-25 16:23:11 +00:00
|
|
|
restart)
|
|
|
|
stop
|
|
|
|
start
|
|
|
|
;;
|
2019-03-29 03:29:30 +00:00
|
|
|
rebuild)
|
|
|
|
rebuild
|
|
|
|
;;
|
2013-11-25 16:23:11 +00:00
|
|
|
condrestart)
|
2011-07-06 19:25:34 +00:00
|
|
|
;;
|
2013-11-25 16:23:11 +00:00
|
|
|
propagate)
|
|
|
|
propagate_ssh_key
|
2011-07-06 19:25:34 +00:00
|
|
|
;;
|
2018-05-11 02:02:39 +00:00
|
|
|
showmem)
|
|
|
|
show_reserved_mem
|
|
|
|
;;
|
2021-04-21 19:27:10 +00:00
|
|
|
estimate)
|
|
|
|
do_estimate
|
|
|
|
;;
|
2021-06-10 05:06:22 +00:00
|
|
|
reset-crashkernel)
|
|
|
|
reset_crashkernel "$2"
|
|
|
|
;;
|
2013-11-25 16:23:11 +00:00
|
|
|
*)
|
2021-06-10 05:06:22 +00:00
|
|
|
dinfo $"Usage: $0 {estimate|start|stop|status|restart|reload|rebuild|reset-crashkernel|propagate|showmem}"
|
2013-11-25 16:23:11 +00:00
|
|
|
exit 1
|
2011-07-06 19:25:34 +00:00
|
|
|
esac
|
2013-11-25 16:23:11 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
# Other kdumpctl instances will block in queue, until this one exits
|
|
|
|
single_instance_lock
|
|
|
|
|
|
|
|
# To avoid fd 9 leaking, we invoke a subshell, close fd 9 and call main.
|
|
|
|
# So that fd isn't leaking when main is invoking a subshell.
|
2021-06-10 05:06:22 +00:00
|
|
|
(exec 9<&-; main "$@")
|
2011-07-06 19:25:34 +00:00
|
|
|
|
|
|
|
exit $?
|