Bugzilla – Bug 1019590
kdump crash simulation cause root FS corruption
Last modified: 2018-04-17 13:59:24 UTC
1. Install and setup kdump 2. Press Alt + SysRQ + C to simulate a crash ==> kdump will start collecting dump but instead of write it into defined place it will start fsck to check root fs . RESULT : - dump not written into /var/crash - root fs contain serious errors which not allowed me to boot system until I fix them with manual fsck execution on detached root fs Was able to reproduce this two times in a row IMO this allow to exclude possibility that I had corrupted fs before simulation of crash. # zypper info kdump Information for package kdump: ------------------------------ Repository : Main Repository (OSS) Name : kdump Version : 0.8.15-29.1 Arch : x86_64 Vendor : openSUSE Installed Size : 644.2 KiB Installed : Yes Status : up-to-date # cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.4.41-1.g3bf02b3-default root=UUID=ba62de1c-0dc0-4c0b-b018-7fac7a19d548 resume=/dev/disk/by-uuid/7f1942a6-291b-4f72-883b-e1295bf1f53d showopts crashkernel=256M # cat /usr/lib/systemd/system/kdump.service [Unit] Description=Load kdump kernel on startup After=local-fs.target Wants=kdump-rebuild-initrd.service [Service] Type=oneshot ExecStart=/lib/kdump/load.sh ExecStop=/lib/kdump/unload.sh RemainAfterExit=true [Install] WantedBy=multi-user.target
Petr, could you take a look? There seems something strange in kdump package. Running fsck in kdump initrd sounds bad. openSUSE Leap 42.2 kdump package is basically identical with SLE12-SP2, so the same issue should exist on SLE12-SP2, too.
Just to stay on same page : problem is not that fsck is executed during getting the dump. Actually running fsck more or less expected , fsck runs because root fs is corrupted . Main problem is in a fact that root fs is corrupted potentially due to crash simulation.
Petr is on long time leave vacation, Lance Wang is taking over Kdump maintaining work, re-assigned to him.
This is automated batch bugzilla cleanup. The openSUSE 42.2 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or you can still observe it under openSUSE Leap 15.0, please feel free to reopen this bug against that version (see the "Version" component in the bug fields), or alternatively open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime