Skip to content

kdumpctl: Deprecate raw dump targets #149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
licliu wants to merge 1 commit into
base: main
Choose a base branch
from
+13 −9
Open

kdumpctl: Deprecate raw dump targets #149

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions gen-kdump-conf.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,9 +27,9 @@ generate()
# overwritten to the default crahskernel value.
#
# raw <partition>
# - Will dd /proc/vmcore into <partition>.
# Use persistent device names for partition devices,
# such as /dev/vg/<devname>.
# - 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 <nfs mount>
# - Will mount nfs to <mnt>, and copy /proc/vmcore to
Expand Down Expand Up @@ -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
Expand Down
10 changes: 6 additions & 4 deletions kdump.conf.5
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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.

Expand Down Expand Up @@ -53,13 +53,15 @@ Also see kdumpctl(8).
.B raw <partition>
.RS
Will dd /proc/vmcore into <partition>. Use persistent device names for
partition devices, such as /dev/vg/<devname>.
partition devices, such as /dev/vg/<devname>. 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
Comment on lines 55 to 59
Copy link
Copy Markdown
Collaborator

@prudo1 prudo1 Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same like above in gen-kdump-conf.sh


.B nfs <nfs mount>
.RS
Will mount nfs to <mnt>, and copy /proc/vmcore to <mnt>/<path>/%HOST-%DATE/,
supports DNS. Note that a fqdn should be used as the server name in the
supports DNS. Note that a fqdn should be used as the server name in the
mount point.
.RE

Expand Down
1 change: 1 addition & 0 deletions kdumpctl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 3 additions & 1 deletion kexec-kdump-howto.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Comment on lines 451 to 456
Copy link
Copy Markdown
Collaborator

@prudo1 prudo1 Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just for completion. Ideally we would use the same phrasing like in gen-kdump-conf.sh and the man page. But that would require to adjust the Dedicated file system section as well as it references this section. Personally I think that is too much for the deprecation and should be done when we remove the code. At that point we'll need to make more adjustments to kexec-kdump-howto.txt anyway. So I'm fine with keeping it this way.


Similar to raw partition dumping, you can format a partition with the file
Expand Down Expand Up @@ -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
Expand Down
Loading