On Mon, May 19, 2014 at 03:45:27PM +0800, WANG Chao wrote:
[..]
> IIUC, if for whatever reason some dracut service fails, systemd
will
> continue to boot and if need be fail much later and put user into
> emergecny shell.
>
> That means if we fall into kdump emergency handler, we have already
> tried to run dracut-initqueue already. And either it succeeded or it
> failed.
No, this is not right. Error could happen at any point of the boot
process. We can't guarantee dracut-initqueue is already started when
drop into kdump error handler.
Does current code do that? I did a quick grep of current code and could
not see emergency hanlder being invoked early.
So that means that emergency handler will be invoked much later, even if
error happens before dracut-initqueue. And that also means that
dracut-initqueue will be either run by then or failed by then.
So are you able to reproduce this that you fall into kdump handler and
dracut-initqueue has not run yet. Can you let me know how do you get
there. Or you are just future proofing the code.
Thanks
Vivek