Bug#873613: systemd gets confused at shutdown time

[Felipe Sateler]

On Wed, Aug 30, 2017 at 6:53 AM, Harald Dunkel <harald.dunkel at aixigo.de>
wrote:

> On Tue, 29 Aug 2017 11:17:03 -0300
> Felipe Sateler <fsateler at debian.org> wrote:
> >
> > Please attach the full configuration for your mount points.
> >
>
> /proc/mounts is attached (as it is now).
>

Looks like your nfs mounts are missing the _netdev option. Does the problem
persist if you add that option? Is this generated from fstab or mount units?


>
> > > Basic problem seems to be indicated by the message
> > >
> > >         nfs: server nfs-home not responding, timed out
> > >
> >
> > Looks like systemd shut down your network before it unnmounted remote
> > filesystems.
> >
>
> Maybe it should have tried to run "umount -f" or to kill user processes
> keeping the mount point busy? Anyway, if you look at the log file you
> will notice that portmap was stopped *very* early at shutdown time, even
> though /home was still mounted via NFS.
>
> >
> > Could you attach full logs? Attaching the info generated by reportbug
> > would be useful too.
> >
>
> journalctl.log is attached (in ASCII). Unfortunately journald stopped
> logging. The long delay at shutdown time doesn't show, but I took a
> photo.
>

The full info that reportbug would have generated is important. Please
attach it.

-- 

Saludos,
Felipe Sateler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170830/36de7f79/attachment-0002.html>