[systemd-devel] fstab mounts get unmounted during boot (.device unit bouncing?)

[Lennart Poettering]

On Wed, 11.02.15 13:20, Martin Pitt (martin.pitt at 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
> | [    5.629559] donald systemd[1]: Unit home.mount is bound to
> | inactive service. Stopping, too.

Which unit precisely is the mount unit bound to? Is this the device
unit change we recently made?

(The log message is misleading, it talks specifically of a "service",
but actually means generically "unit"...)

My guess is that the device unit the mount unit is bound to doesn't
actually become active... Maybe a different name is used for it or so=

> | [    5.629561] donald systemd[1]: Trying to enqueue job home.mount/stop/fail
> | [    5.629569] donald systemd[1]: Installed new job home.mount/stop as 3
> | [    5.629573] donald systemd[1]: Enqueued job home.mount/stop as 3
> | [    5.630230] donald systemd[1]: Job home.mount/stop finished, result=canceled
> | [    5.630232] donald systemd[1]: Installed new job home.mount/start as 27
> | [    5.630437] donald systemd[1]: Installed new job dev-disk-by\x2duuid-f86539b0\x2d3a1b\x2d4372\x2d83b0\x2dacdd029ade68.device/start as 26
> | [    5.630536] donald systemd[1]: Expecting device dev-disk-by\x2duuid-f86539b0\x2d3a1b\x2d4372\x2d83b0\x2dacdd029ade68.device...
> | [    6.663570] donald systemd[1]: dev-disk-by\x2duuid-f86539b0\x2d3a1b\x2d4372\x2d83b0\x2dacdd029ade68.device changed dead -> plugged
> | [    6.663795] donald systemd[1]: Job dev-disk-by\x2duuid-f86539b0\x2d3a1b\x2d4372\x2d83b0\x2dacdd029ade68.device/start finished, result=done
> | [    6.672264] donald systemd[1]: Job home.mount/start finished, result=done
> | [    7.077082] donald systemd[1]: home.mount changed mounted -> dead
> | [    9.151474] donald systemd[1353]: dev-disk-by\x2duuid-f86539b0\x2d3a1b\x2d4372\x2d83b0\x2dacdd029ade68.device changed dead -> plugged
> | [   21.932586] donald systemd[2069]:
> | dev-disk-by\x2duuid-f86539b0\x2d3a1b\x2d4372\x2d83b0\x2dacdd029ade68.device
> | changed dead -> plugged

The latter two are from a systemd --user instance, see the PIDs...

> | BindsTo=dev-disk-by\x5cx2duuid-f86539b0\x5cx2d3a1b\x5cx2d4372\x5cx2d83b0\x5cx2dacdd029ade68.device

It would be goot to check what this .device unit is up to...


Lennart

-- 
Lennart Poettering, Red Hat