Bug#843063: systemd: does not show failed nfs mount when nfs server not available on booting the client

[Felipe Sateler]

On 3 November 2016 at 12:31, Martin Steigerwald
<martin.steigerwald at teamix.de> wrote:
> Package: systemd
> Version: 215-17+deb8u5
> Severity: important
>
> Dear Martin, dear Michael, dear Maintainer,
>
> On preparing a reference setup for a new Linux training I work on I found
> that if I start a client with an NFS mount with _netdev in /etc/fstab, but
> without nofail, while the NFS server is not available, Systemd will try to
> mount the export, yet after 90 seconds it not only continues booting, but
> also does not *see* the failed mount.

I suspect the problem is [1] fixed by [2] (will be present in 232).

Hint is this:

> root at webserver01:~# systemctl status srv-web.mount
> ● srv-web.mount - /srv/web
>    Loaded: loaded (/etc/fstab)
>    Active: active (mounted) (Result: timeout) since Do 2016-11-03 16:03:09 CET; 21min ago
>     Where: /srv/web
>      What: fileserver:web
>      Docs: man:fstab(5)
>            man:systemd-fstab-generator(8)
>
> Nov 03 16:01:39 webserver01 systemd[1]: Mounting /srv/web...
> Nov 03 16:03:09 webserver01 systemd[1]: srv-web.mount mounting timed out. Stopping.
> Nov 03 16:03:09 webserver01 systemd[1]: Mounted /srv/web.
>

You report this from jessie, which of course is not going to get 232.
Maybe backporting this fix is not too hard...

[1] https://github.com/systemd/systemd/issues/4275
[2] https://github.com/systemd/systemd/pull/4337/commits/1f0958f640b87175cd547c1e69084cfe54a22e9d

-- 

Saludos,
Felipe Sateler