Comment # 6 on bug 1156421 from Fabian Vogt

(In reply to Franck Bui from comment #3)
> (In reply to Fabian Vogt from comment #1)
> > Here it switched to /var successfully. So the question is why it does not
> > happen (reliably?) when running during boot?
> 
> Hmm... the only reason I can see is that /var is still a RO partition at the
> time the journal is flushed and therefore the system journal couldn't be
> created in /var.

/var is mounted read-write in the initrd already. So unless something re-mounts
it multiple times during boot, I don't think that's the case.

> But you would get an explicit error on the next reboot since this time the
> journal file was already created when you flushed the journal manually and
> journald would fail at opening it RW.
>
> Can you see such error ?

Nope. The journal seems corrupted though, for some reason.

> (In reply to Franck Bui from comment #4)
> BTW which version of systemd are you running ?

v243 - do you need the full rpm version?

(In reply to Franck Bui from comment #5)
> (In reply to Fabian Vogt from comment #1)
> > I think I can reproduce this here. The issue appears to be that
> > systemd-journal-flush.service runs, but does somehow not cause a flush.
> > 
> 
> Any chance I can reproduce it locally, maybe with qemu ?

Might be possible with software emulation, I'll try.