On 12/09/15 at 04:02pm, Dave Young wrote:
Systemd reports a conflict when kdump calls reboot during booting
"during boot" seems enough. But it doesn't matter much.
because it tries to stop services while they are starting up.
use systemctl reboot -f will fix this problem.
man systemd.service show below:
reboot causes a reboot
following the normal shutdown procedure (i.e. equivalent to systemctl reboot).
reboot-force causes a forced reboot
which will terminate all processes forcibly but should cause no dirty file systems on
reboot (i.e. equivalent to
systemctl reboot -f) and reboot-immediate causes immediate execution of the reboot(2)
system call, which might result in
But during test "/sbin/reboot -f" actually equals to systemctl "reboot -f
Here you means "systemctl reboot -f -f", or "reboot -f -f" in
Test with "reboot -f" I still get below dirty ext2 filesystem:
I didn't get what it means about this line and above line. Which one
[root@localhost ~]# fsck /dev/vdb
fsck from util-linux 2.27
e2fsck 1.42.13 (17-May-2015)
/dev/vdb was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/vdb: 12/128016 files (0.0% non-contiguous), 18474/512000 blocks
Change to systemctl reboot -f will instead get a clean filesystem
"systemctl reboot -f", isn't it?
Thus let's use systemctl reboot -f instead, it will ensure clean filesystem even if
"systemctl reboot -f"? It would be better to use double or singe
quotation to enclose it.
Your mail client didn't get a 80 char wrap around?
other services are not stopped, we do not care.
Since it blocks Fedora rawhide kdump I think we should add this ASAP.
Later I will dig into systemd changes see which commit cause the breakage.
Signed-off-by: Dave Young <dyoung(a)redhat.com
Signed-off-by: Dangyi Liu <dliu(a)redhat.com>
kdump-lib-initramfs.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
@@ -6,14 +6,14 @@ KDUMP_PATH="/var/crash"
DEFAULT_CORE_COLLECTOR="makedumpfile -l --message-level 1 -d 31"
+DEFAULT_ACTION="systemctl reboot -f"
+FINAL_ACTION="systemctl reboot -f"
@@ -57,7 +57,7 @@ get_kdump_confs()
+ DEFAULT_ACTION="systemctl reboot -f"
Code looks good based on the quatation of systemd.service paragraph.
> kexec mailing list