It seems like the upstream commits to fix this may have made journalctl --flush flaky and/or introduced other regressions: https://github.com/systemd/systemd/pull/12230#issuecomment-491593897
Additionally, the fix upstream is not a trivial backport and has the potential to cause even more problems for SRU releases. https://github.com/systemd/systemd/pull/12230/commits As this bug is rather limited in scope (only systems with /var or /var/log mounted separately from /) and the only potential issue I see is /var isn't cleanly unmounted, it seems like backporting the upstream fix may bring more problems than it solves. Possibly there is some simpler workaround we could add for SRU releases, but it would take some more investigation. I'm removing myself as bug owner here, so possibly someone else can investigate, in case I'm not able to get back to this. ** Tags removed: ddstreet-next ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => New ** Changed in: systemd (Ubuntu Cosmic) Status: In Progress => New ** Changed in: systemd (Ubuntu Disco) Status: In Progress => New ** Changed in: systemd (Ubuntu Eoan) Status: In Progress => New ** Changed in: systemd (Ubuntu Bionic) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Cosmic) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Disco) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Eoan) Assignee: Dan Streetman (ddstreet) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788048 Title: systemd journald failed unmounting var To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1788048/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
