On Tue, Apr 29, 2014 at 03:10:02PM +0200, Michael Biebl wrote: > Am 29.04.2014 13:10, schrieb Jason Alavaliant: > > On 2014-04-29 22:36, Michael Biebl wrote: > >> Am 29.04.2014 11:31, schrieb Jason Alavaliant: > > >> Do you have an NFS / remote fs configuration in your /etc/fstab? > > > > Yes I've got a nfs4 mounted home directory > > server.local:/ /home nfs4 defaults 0 0 > > I suspect the hang to be caused by the NFS fstab entry. Can you comment > out the entry and reboot so we have confirmation?
I got the same issue, and I don't have a bridge interface, but I do have a NFS entry in /etc/fstab. Disabling it makes the reboot to succeed. Given that systemd is now the default, if every persons with an NFS entry in fstab will get their systems broken, it might be a good idea to increase the severity of this bug. > If so, can you please try the following patch for > /etc/network/if-up.d/mountnfs with the NFS mount re-enabled. > > --- a/network/if-up.d/mountnfs > +++ b/network/if-up.d/mountnfs > @@ -7,6 +7,10 @@ > # Also mounts SMB filesystems now, so the name of > # this script is getting increasingly inaccurate. > > +if [ -d /run/systemd/system ] ; then > + systemctl status network.target > /dev/null || exit 0 > +fi > + > PATH=/sbin:/bin > . /lib/init/vars.sh This patch works for me, thanks. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
