Hi, angry rectangle skribis: > Since the upgrade to shepherd 0.9, I get "recovering journal" every single time I start my computer. > To be specific, "recovering journal" appears after I enter my encryption password in the initrd. > I assume this means the filesystem wasn't cleanly unmounted. > I am doing a proper shutdown, using either "reboot" or "halt." I can see that as well. > The guix commit 400c9ed3d779308e56038305d40cd93acb496180 is the specific commit that upgrades shepherd and causes me this problem. The previous commit is fine. > I'm can confirm that it's still broken on recent commits. I'm on 696e2cc345f015c32f211bf0d0330c04b1cf5f15. Preliminary investigation suggests this is because shepherd doesn’t close log files beforehand (in 0.9, those specified as #:log-file to ‘make-forkexec-constructor’ & co. are opened by PID 1; conversely, shepherd 0.8 would open them in the child process.) To be continued… Thanks for reporting the issue and finding the offending commit! Ludo’. PS: Below my (ugly) debugging tricks for posterity. To see those messages, you typically need to start a VM with ‘-serial stdio’ and pass “console=ttyS0” to the kernel. (It’s best to start a standalone VM with an image created by ‘guix system image -t qcow2’.)