Re: Antw: Re: Antw: [EXT] Infinite loop at startup on var fsck failure

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mi, 26.02.20 10:55, Ulrich Windl (Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx) wrote:

> > I suspect that the real problem is, that fsck failed to fix the file
> > system, so as a result, systemd tried repeatedly to start the fsck job
> > for /var as var.mount was pulled in as a dependency (e.g. for
> > journald).
>
> The exit code should help:
>        The exit code returned by fsck is the sum of the following conditions:
>             0    - No errors
>             1    - File system errors corrected
>             2    - System should be rebooted
>             4    - File system errors left uncorrected
>             8    - Operational error
>             16   - Usage or syntax error
>             32   - Fsck canceled by user request
>             128  - Shared library error

We check the exit code.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel