Re: [PATCH] Don's try to restart dracut-initqueue if it's already failed

[piliu]

On 12/02/2020 09:45 AM, Kairui Song wrote:
> 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 now work if first attemp failed.
>
> So just try to start sysroot.mount, if it failed, there is no luck.
> Signed-off-by: Kairui Song
>
> kdump-lib-initramfs.sh | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kdump-lib-initramfs.sh b/kdump-lib-initramfs.sh
> index 9275c83..791d141 100755
> --- a/kdump-lib-initramfs.sh
> +++ b/kdump-lib-initramfs.sh
> @@ -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

Acked-by: Pingfan Liu