On Sun, 23.09.12 17:21, Bardur Arantsson ([email protected]) wrote: > Hi all, > > (Hopefully this list is appropriate for this -- please let me know if > there's a more appropriate one.) > > I'm having a little trouble with NFS mounts when starting them via > systemd, but I'm hoping that I may have missed something obvious. > > Here's the snippet from /etc/fstab: > > 192.168.0.1:/srv/vg0p-data /data nfs \ > defaults,proto=tcp,nfsvers=4,vers=4,noauto 0 1 > > (Line split here for readability, it's a single line in the actual file.) > > When I run > > # systemctl --version > systemd 189 > arch > +PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT \ > +LIBCRYPTSETUP +GCRYPT +ACL +XZ > > # systemctl start data.mount > > I get the output > > A dependency job failed. See system journal for details. > > after a longish timeout (guessing it's the default 90s). In the journal > I get: > > Sep 23 17:08:45 gwendolyn systemd[1]: Job > 192.168.0.1:-srv-vg0p\x2ddata.device/start timed out. > Sep 23 17:08:45 gwendolyn systemd[1]: Job data.mount/start failed with > result 'dependency'.
This indicates a bug i systemd actually. For some reason systemd appears to believe that your NFS share is a device to wait for. I tried to fix this in git with two commits. Please test! Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
