Don's try to restart dracut-initqueue if it's already failed
If dracut-initqueue failed in kdump kernel and failure action is set to dump_to_rootfs, there is no point try again to start the initqueue. It will also slow down the dump process, and the initqueue will most like still not work if first attemp failed. So just try to start sysroot.mount, if it failed, there is no luck. Signed-off-by: Kairui Song <kasong@redhat.com> Acked-by: Pingfan Liu <piliu@redhat.com>
This commit is contained in:
parent
eaf0e813a2
commit
ad6a93b00d
@ -222,7 +222,8 @@ dump_to_rootfs()
|
||||
{
|
||||
|
||||
dinfo "Trying to bring up rootfs device"
|
||||
systemctl start dracut-initqueue
|
||||
systemctl is-failed dracut-initqueue || systemctl start dracut-initqueue
|
||||
|
||||
dinfo "Waiting for rootfs mount, will timeout after 90 seconds"
|
||||
systemctl start sysroot.mount
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user