[systemd-devel] journal on btrfs subvolume, failed unmounting /var/log/journal

Lennart Poettering lennart at poettering.net
Fri Feb 14 03:19:33 PST 2014

On Tue, 11.02.14 21:02, Chris Murphy (lists at colorremedies.com) wrote:

> It looks like var-log-journal.mount is called before systemd-journald
> is finished using it. Is the failure message merely cosmetic? The file
> system comes up clean on reboot so I'm pretty sure it's being cleanly
> unmounted despite this message.

Yeah, there's a bit of an ugliness here: journald stays running until
the final killing spree which keeps the fs busy. The main reason for
that is simply that we have no nice way to tell journald synchronously
that it should stop access to /var and continue logging into
/run. Normally we'd use dbus for requesting this, but since dbus-daemon
is a client of journald and we really can't have the cyclic dep betwen
journald and dbus-daemon we cannot make journald be on the bus. With the
advent of kdbus this will change however, as then we have dbus around
all the time, and the cyclic dep is gone. 

The issue is mostly cosmetic as we still will cleanly unmount all
remaining file systems right before shutting down. We will also cleanly
terminate journald then. 


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list