From f6ab755d5daf3b0ebfcad61b9213713f5e57b781 Mon Sep 17 00:00:00 2001 From: Lichen Liu Date: Fri, 20 Mar 2026 10:14:11 +0800 Subject: [PATCH] kdumpctl: Deprecate raw dump targets The raw dump target (using dd to a partition) is being phased out in favor of filesystem-based targets. This patch adds deprecation warnings to the documentation and runtime scripts to alert users that support will be removed in a future release. Resolves: https://redhat.atlassian.net/browse/KEX-516 Assisted-by: Google Gemini Signed-off-by: Lichen Liu --- gen-kdump-conf.sh | 7 +++---- kdump.conf.5 | 10 ++++++---- kdumpctl | 1 + kexec-kdump-howto.txt | 4 +++- 4 files changed, 13 insertions(+), 9 deletions(-) diff --git a/gen-kdump-conf.sh b/gen-kdump-conf.sh index eaacc8a6..9dffa8af 100755 --- a/gen-kdump-conf.sh +++ b/gen-kdump-conf.sh @@ -27,9 +27,9 @@ generate() # overwritten to the default crahskernel value. # # raw -# - Will dd /proc/vmcore into . -# Use persistent device names for partition devices, -# such as /dev/vg/. +# - The 'raw' dump target is deprecated and will be removed in a future +# release. Please migrate to a filesystem-based dump target (e.g., ext4, +# xfs, nfs, or ssh). # # nfs # - Will mount nfs to , and copy /proc/vmcore to @@ -178,7 +178,6 @@ generate() # (this option is mandatory to enable fence_kdump). # -#raw /dev/vg/lv_kdump #ext4 /dev/vg/lv_kdump #ext4 LABEL=/boot #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937 diff --git a/kdump.conf.5 b/kdump.conf.5 index 591d9ece..8614fdc9 100644 --- a/kdump.conf.5 +++ b/kdump.conf.5 @@ -3,7 +3,7 @@ .SH NAME kdump.conf \- configuration file for kdump kernel. -.SH DESCRIPTION +.SH DESCRIPTION kdump.conf is a configuration file for the kdump kernel crash collection service. @@ -16,7 +16,7 @@ effect, restart the kdump service to rebuild the initrd. For most configurations, you can simply review the examples provided in the stock /etc/kdump.conf. -.B NOTE: +.B NOTE: For filesystem dumps the dump target must be mounted before building kdump initramfs. @@ -53,13 +53,15 @@ Also see kdumpctl(8). .B raw .RS Will dd /proc/vmcore into . Use persistent device names for -partition devices, such as /dev/vg/. +partition devices, such as /dev/vg/. The "raw" dump target is +deprecated and will be removed in a future release. Please migrate to a +filesystem-based dump target (e.g., ext4, xfs, nfs, or ssh). .RE .B nfs .RS Will mount nfs to , and copy /proc/vmcore to //%HOST-%DATE/, -supports DNS. Note that a fqdn should be used as the server name in the +supports DNS. Note that a fqdn should be used as the server name in the mount point. .RE diff --git a/kdumpctl b/kdumpctl index 835f3f08..bccf6799 100755 --- a/kdumpctl +++ b/kdumpctl @@ -350,6 +350,7 @@ parse_config() fi ;; raw) + dwarn "The 'raw' dump target is deprecated and will be removed in a future release. Please migrate to a filesystem-based dump target (e.g., ext4, xfs, nfs, or ssh)." if [[ -d "/proc/device-tree/ibm,opal/dump" ]]; then dwarn "Won't capture opalcore when 'raw' dump target is used." fi diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt index d2e41869..5786afa3 100644 --- a/kexec-kdump-howto.txt +++ b/kexec-kdump-howto.txt @@ -451,6 +451,8 @@ onto partition /dev/vg/lv_kdump. Restart the kdump service via initrd. Dump target should be persistent device name, such as lvm or device mapper canonical name. +Raw targets will be deprecated in a future version. + 2) Dedicated file system Similar to raw partition dumping, you can format a partition with the file @@ -901,7 +903,7 @@ Currently, only x86_64 supports encrypted dump target. And depending on your setup, you may need to run "kdumpctl setup-crypttab" once in order for kdump.service to work on boot automatically next time. You can confirm if this step is needed by running "kdumpctl restart". If you have -to input passphrase to unlock the encrypted volume, then please run +to input passphrase to unlock the encrypted volume, then please run "kdumpctl setup-crypttab". For other architectures, kdump is not working well. First, user have