-
Notifications
You must be signed in to change notification settings - Fork 1
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
Include initrd mounts in the final system also #3
Conversation
Without this, things like `RequiresMountsFor` do not work correctly during shutdown. See systemd/systemd#34327
eb99962
to
3fae1ab
Compare
It seems like this change would re-introduce the ordering cycle for Adding an entry in the integration test for /var/log with I'm not sure yet how to resolve this, other than the solution described at the end of the linked file. |
I booted my system with this and didn't get any mention of a cycle in my logs. |
The mount is still set up in initrd as before, it's just that we include the unit in the final system as well so that systemd takes it into account and uses the right ordering when unmounting. |
I just pushed another branch based on yours where |
It's so weird that I don't have that cycle on my systems, I just checked again. I have the whole shutdown sequence in the logs and there's no mention of any cycle. I will try to find out what is different, something in my config must be preventing this cycle. I'm running nixos-unstable (with a bunch of unmerged PRs patched in). I already notice that actually now there isn't any mention of unmounting /var/log or /var/lib on shutdown of my machine, neither of stopping systemd-journal-flush. They might only get unmounted after the journal already stopped, since the last message that I have is "Journal stopped". |
This should be solved by 97104c0. |
Cool, I'll give that a try, thanks for your work on this! |
Seems to be working well now, thanks! |
Without this, things like
RequiresMountsFor
do not work correctly during shutdown.See systemd/systemd#34327
Fixes #2