"systemctl isolate emergency" fails to stop systemd-journald..

it's not an upstream issue since the problem does not occurr with other
distributions.

having systemd-journald to be stopped is desirable since the
administrator can then use e2fsck to repair filesystems(after the
problematic filesystem read-only -- "mount -o ro,remount /" for instance)

upstream won't look into this because it is not happening on other
distributions.

please take a look
thanks

Am 02.06.22 um 00:49 schrieb westlake:

It is an upstream issue. The Debian project does not ship any patches in
that regard which would change the behaviour of systemd.

Please don't file duplicates
You already filed this as #999695

I see that you still haven't forwarded this upstream, so it's unlikely
to be fixed.

Michael

I discussed this with upstream in the context of
https://github.com/systemd/systemd/pull/23863#issuecomment-1169866253

They rejected the idea of automatically stopping journald when entering
rescue mode. The correct way of making journald stop logging to /var
(and keeping /var or / busy), is to use `journalctl --relinquish-var` in
the case you want to fsck those file systems.


Michael