-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Centos: systemd-journald.service misses the zfs-mount.service dependency #8060
Comments
This is not an issue for ZoL just a matter of proper configuration on your side. Simply put override file for each unit that depends on your mount point:
For journald that will be: |
Well, you're right - yeah, that's a minor issue, but wouldn't it be great if this override.conf file was included in the centos package ? |
Nope, the fact that you have |
Same rule applies to your approach - the fact that you don't have the /var/log on a separate dataset doesn't mean everyone shouldn't have it there. In fact, most modern installers provided with ZFS-enabled OSes do configure the /var/log on a separate dataset: Solaris does, FreeBSD does.... welll, that's the end of list for now, but this pretty much means that any user migrating his habits from these OSes to Linux will want /var/log on a separate dataset (I could go much further and say that I believe everyone should have the /var/log on a separate dataset, but that would be counterproductive). And what harm could be done by starting journald after the zfs-mount.service ? I see none. I see that the defaults provided currently are non-universal and hard to fix by newbies. |
Do you ship predefined |
Rather than adding an override for each unit, you can make I have this in the Ubuntu 18.04 HOWTO:
|
ZFS has a systemd mount generator these days. |
System information
Describe the problem you're observing
systemd-journald.service misses the zfs-mount.service dependency. Thus, when /var/log is on a separate dataset (pretty much the standard nowadays) at the moment zfs-mount service is starting, /var/log isn't empty, because journald has already put the files there.
Describe how to reproduce the problem
Make /var/log reside on a separate dataset inside the root pool, and attempt to boot the system. Some of jourlald services (socket, flush-to-persistent-storage and journald itself will be in a failed state).
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: