On Tue, 20.11.12 15:23, Alexander Vladimirov (alexander.idkfa.vladimi...@gmail.com) wrote:
> > > I was able to fix it using simple patch (http://pastie.org/5380592) > > which > > > makes systemd ignore root mount when running in container. > > > > Hmm, the code in mount_points_list_umount() in umount.c already exlcudes > > / and /usr from all unmounting? > > > Yes, it does, but those filesystems are counted as failed then, and systemd > reports that it cannot unmount all filesystems. > I was guessing if it could be the reason why journal gets corrupted and it > turns out it's not. > It still seems a bit useful, since it prevents systemd from printing > cryptic warnings about failed unmounts without actual filesystem name. > > > > > > The second issue is journald reporting journal corruption on every > > > container boot, regardless of clean shutdown. This also happens when I > > > bind-mount hosts journal directory into container. > > > > Hmm, this is interesting. Do you see any messages about journal shutting > > down in the journal? > > > That's what container's journal look like after shutdown: > http://pastie.org/private/njgmtyxdglrpx3qxspufog, > there's no warnings or errors on console during or after shutdown. Could you file two fdo bugs about issues? This both looks like stuff to fix properly. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel