[Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

Max-Ulrich Farber 1577885 at bugs.launchpad.net
Wed May 25 17:05:58 UTC 2016

In https://wiki.archlinux.org/index.php/talk:NFS#NetworkManager-wait-
online I found a workaround that works for me (ArchLinux has been using
systemd for a long time already):

 * create a file /lib/systemd/system/auto_share.service with the following contents:

 * execute the following commands in a terminal:
     systemctl enable NetworkManager-wait-online
     systemctl reenable auto_share.service 

Having done this once, booting and shutdown works fine, even with still
mounted cifs shares. It stays the same after system reboot.

Even if this workaround will work fine for everyone (?), this bug should
be fixed permanently anyhow!

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.

  120sec delay during shutdown or reboot with still mounted cifs (via

Status in network-manager package in Ubuntu:
Status in systemd package in Ubuntu:

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  // /media/server/server_data cifs

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list