On 12/11/15 at 01:13pm, Baoquan He wrote:
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:
>
> [snip]
> 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
> data loss.
> [snip]
>
> But during test "/sbin/reboot -f" actually equals to systemctl
"reboot -f -f"
Here you means "systemctl reboot -f -f", or "reboot -f -f" in
systemctl?
I meas "systemctl reboot -f -f" should quote systemctl along with reboot -f -f
>
> 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
doesn't work.
reboot -f does not work, Dangyi's v1 use reboot -f
My test result is:
reboot -f == systemctl reboot -f -f == directly reboot without umount
But in this v2 patch I use
systemctl reboot -f which will umount filesystem
Thanks
Dave