<div dir="ltr">On Thu, Jul 18, 2019 at 5:02 PM Chris Murphy <<a href="mailto:lists@colorremedies.com">lists@colorremedies.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Jul 18, 2019 at 10:18 AM Dave Howorth <<a href="mailto:systemd@howorth.org.uk" target="_blank">systemd@howorth.org.uk</a>> wrote:<br>
><br>
> On Thu, 18 Jul 2019 09:55:51 -0600<br>
> Chris Murphy <<a href="mailto:lists@colorremedies.com" target="_blank">lists@colorremedies.com</a>> wrote:<br>
> > On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala <<a href="mailto:uoti.urpala@pp1.inet.fi" target="_blank">uoti.urpala@pp1.inet.fi</a>><br>
> > wrote:<br>
> > ><br>
> > > On Mon, 2019-07-15 at 14:32 -0600, Chris Murphy wrote:<br>
> > > > So far nothing I've tried gets me access to information that would<br>
> > > > give a hint why systemd-journald thinks there's no free space and<br>
> > > > yet it still decides to create a single 8MB system journal, which<br>
> > > > then almost immediately gets deleted, including all the evidence<br>
> > > > up to that point.<br>
> > ><br>
> > > Run journald under strace and check the results of the system calls<br>
> > > used to query space? (One way to run it under strace would be to<br>
> > > change the unit file to use "strace -D -o /run/output<br>
> > > systemd-journald" as the process to start.)<br>
> ><br>
> > It's a good idea but strace isn't available on Fedora live media. So I<br>
> > either have to learn how to create a custom live media locally (it's a<br>
> > really complicated process) or convince Fedora to add strace to live<br>
> > media...<br>
><br>
> I'm not a fedora user, but I don't think it's that difficult to run<br>
> strace.<br>
><br>
> To run it once, start your live image and type:<br>
><br>
> # yum install strace<br>
><br>
> You will need to reinstall it if you reboot.<br>
><br>
> To permanently install it apparently you need to configure your USB<br>
> with persistent storage. I haven't looked up how to do that.<br>
<br>
I thought about that, but this is a substantial alteration from the<br>
original ISO in terms of the storage layout and how everything gets<br>
assembled. But it's worth a shot. If it is a systemd bug, then it<br>
should still reproduce. If it doesn't reproduce, then chances are it's<br>
some kind of assembly related problem.<br>
<br>
Still seems like a systemd-journald bug that neither forward to<br>
console nor to kmsg includes any useful systemd or dracut debugging.<br>
</blockquote><div><br></div><div style="font-family:monospace,monospace" class="gmail_default">I'm no systemd expert by any means, and just a Fedora user because we ship our product on RHEL, so I like to see what is coming down the pipe. Nonetheless, I have been following this thread with interest since threads I always follow on LKML refer to the kernel's shitty print to console implementation that sucks so bad and well, it might cross boundaries..<br></div><div style="font-family:monospace,monospace" class="gmail_default"><br></div><div style="font-family:monospace,monospace" class="gmail_default">Not to toss knives, but I would almost always blame RedHat before anyone else in the community - they do have a tendency to bastardize things in ways that suit themselves. Please do not take that as a jab, it just is what it is - like I said - I have just learned to accept it. </div><div style="font-family:monospace,monospace" class="gmail_default"><br></div><div style="font-family:monospace,monospace" class="gmail_default">I am assuming you have ripped apart the initramfs to see exactly how RedHat is invoking systemd in the live images? <br></div><div style="font-family:monospace,monospace" class="gmail_default"><br></div><div style="font-family:monospace,monospace" class="gmail_default">-Greg<br></div></div></div>