On Wed, 11.02.15 13:45, Martin Pitt (martin.p...@ubuntu.com) wrote: > Lennart Poettering [2015-02-11 13:29 +0100]: > > On Wed, 11.02.15 13:20, Martin Pitt (martin.p...@ubuntu.com) wrote: > > > > > Hello all, > > > > > > for a few weeks now (roughly since upgrading to 218) I often end up > > > with my /home and /srv (from fstab) not mounted after booting, and I > > > have to run "mount -a" manually. Initially I attributed this to my > > > hacked-up laptop, but now I got a report from another user about that > > > too (https://launchpad.net/bugs/1419623) > > > > > > The issue is that home.mount (from systemd-fstab-generator) does seem > > > to get mounted, but unmounted immediately afterwards: > > > > > > The full journal and output of systemctl show/status is at > > > http://people.canonical.com/~pitti/tmp/debug-fstab-unmount/ but > > > limiting it to the partition which has /home, and the mount unit > > > reveals some strange things: > > > > > > | $ egrep 'f8653.*device|home.mount' journal.txt > > > | [ 5.629480] donald systemd[1]: home.mount changed dead -> > > > | mounted
Actually, the fact that the unit changes directly from "dead" to "mounted" is interesting. The unit does not go through "mounting", which means that it's not the unit that is invoking the /bin/mount command for this but something else.. Do you see anything about this in the logs? > I wasn't able to reproduce that in QEMU with BIOS; I'm using EFI on my > box which might be a significant difference. Maybe fallout from the GPT auto-discovery? if you turn that off, does it work then? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
