On 12/11/15 at 01:39pm, Dave Young wrote:
On 12/11/15 at 01:19pm, Minfei Huang wrote:
> Hi, Dave.
>
> I am fine with this patch. It is more appropriate if you can add the
> comment log that systemd will umount device to avoid data corruption.
>
> Thanks
> Minfei
>
> On 12/09/15 at 04:02pm, Dave Young wrote:
> > Systemd reports a conflict when kdump calls reboot during booting
> > 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]
Above is the systemd documentation you mentioned,
-f means reboot-force
-f -f means reboot-immediate
Will describe and mention please refer to man systemctl instead of quote
them in the update patch.
-f, --force
When used with enable, overwrite any existing conflicting symlinks.
When used with halt, poweroff, reboot or kexec, execute the
selected operation without shutting down all units. However, all
processes will be killed forcibly and all file systems are
unmounted or remounted read-only. This is hence a drastic but
relatively safe option to request an immediate reboot. If --force
is specified twice for these operations, they will be executed
immediately without terminating any processes or unmounting any
file systems. Warning: specifying --force twice with any of these
operations might result in data loss.
Thanks
Dave
>
> Thanks
> Dave
> _______________________________________________
> kexec mailing list
> kexec(a)lists.fedoraproject.org
>
http://lists.fedoraproject.org/admin/lists/kexec@lists.fedoraproject.org
>
>