[systemd-devel] early mounts in systemd

[Rick Winscot]

15:31:18 localhost systemd[1]: Dependency failed for Flush Journal to
Persistent Storage.
░░ Subject: A start job for unit systemd-journal-flush.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-journal-flush.service has finished with a
failure.
░░
░░ The job identifier is 38 and the job result is dependency.

At this point, flush is attempting to re-route /run/log/journal to
/var/log/journal ... and the /var partition is not yet mounted. Units
generated for fstab in /run/systemd/generator that manage the mount have an
After=local-fs-pre.target which is too late.

Other dependency errors appear in the log; all with the same root cause. By
the time [ a specified service ] that uses /var is ready, the partition has
not yet been mounted. My solution resolves the /var mount as soon as the
block device is seen by udev - which made all the dependency errors go away.



On Fri, Apr 30, 2021 at 1:46 PM Michael Biebl <mbiebl at gmail.com> wrote:

> Am Fr., 30. Apr. 2021 um 19:42 Uhr schrieb Rick Winscot
> <rick.winscot at gmail.com>:
> >
> > systemd 247
>
> Ok, thanks
>
> > /etc/systemd/journald.conf storage is persistent,
> systemd-journal-flush.service has RequiresMountsFor=/var/log/journal.
> >
> > Mounting /var on a separate read-write partition handles the persistent
> log requirement as well as offloading other read-write operations that can
> no longer live on the rootfs... being read-only.
>
> Sure, but what is the actual problem? I do have systems with a
> separate /var and don't remember any ordering issues / race
> conditions.
> Do you have any error messages / journal logs which show the issue?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20210430/2c6d044c/attachment.htm>