Trying to manually unmount the drive with the network down blocks (with CPU at 100%) indefinitely, or so it appears. I waited 40 minutes and then canceled it because I had to go.
Can't the service which mounts/unmounts NFS (not sure which one that is) be put after NetworkManager? 2015-09-09 13:58 GMT-03:00 Michael Biebl <bi...@debian.org>: > Am 09.09.2015 um 05:09 schrieb Javier Ayres: > > I edited the wpa_supplicant service as you suggested but the issue is > still > > present. > > Hm, right. The issue here is, that you are using NetworkManager.service > to bring up your (wireless) interface. Unfortunately we can't bring up > NetworkManager.service before network.target, so NetworkManager is > stopped before your NFS mount is unmounted, i.e. the ordering is wrong > here. > > For ethernet connections, NetworkManager does not tear down the > connection on stop. For wireless connections, stopping NetworkManager > means you lose your network connection. > > The reason why we can't oder NetworkManager.service before > network.target is this leads to dependency cycles atm due to sysv init > scripts in /etc/rcS > > I've also found that the behavior is not consistent, sometimes it > > waits 90 seconds and sometimes it waits 30 minutes (even after changing > the > > fstab entry). > > If you stop your network connection, how long does "umount /mnt/samsung" > block? > > Michael > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > > -- Javier Ayres