[systemd-devel] Hang when mounting NFS via systemd

Bardur Arantsson spam at scientician.net
Sun Sep 23 08:21:47 PDT 2012


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'.
Sep 23 17:08:45 gwendolyn systemd[1]: Job
systemd-fsck at 192.168.0.1:-srv-vg0p\x2ddata.service/start failed with
result 'dependency'.
Sep 23 17:08:45 gwendolyn systemd[1]: Job
192.168.0.1:-srv-vg0p\x2ddata.device/start failed with result 'timeout'.

(The exact same thing happens on first access if I use automounting, or
if remove "noauto" -- the hang just happens during first access and at
boot time respectively.)

The weird thing is that the mount works perfectly if I just mount normally:

   # mount /data
   # ls -l /data
   total 696
   drwx------  2 root   root     4096 Jul 15  2011 lost+found
   ...

(other content omitted for privacy reasons.)

Any hints/ideas as to what might be wrong? I mean it *should* work, right?

Cheers,



More information about the systemd-devel mailing list