[Bug 1577885] [NEW] 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)
Matthias Laumer
matthias.laumer at web.de
Tue May 3 17:54:57 UTC 2016
Public bug reported:
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 :
//192.168.178.61/data /media/server/server_data cifs
users,uid=1000,gid=1000,username=xxxxx,passwd=xxxxxx,iocharset=utf8,sec=ntlm,noauto,_netdev
0
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 power-button.
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.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: cifs delay nfs shutdown umount
** Description changed:
I prepare for mounting with the following entry in /etc/fstab my
Synology NAS :
//192.168.178.61/data /media/server/server_data cifs
users,uid=1000,gid=1000,username=xxxxx,passwd=xxxxxx,iocharset=utf8,sec=ntlm,noauto,_netdev
0
- After login to unity, I mount it with a bash-script (mount -a)
+ 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 comman "umount /media/server ..."
I have not tested if this also appears when I am connected via ethernet.
I think it is because the 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 power-button.
- Failure can be avaided if I umount the network-drives manually previouse
+ 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.
** Description changed:
- I prepare for mounting with the following entry in /etc/fstab my
- Synology NAS :
+ 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 :
//192.168.178.61/data /media/server/server_data cifs
users,uid=1000,gid=1000,username=xxxxx,passwd=xxxxxx,iocharset=utf8,sec=ntlm,noauto,_netdev
0
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 comman "umount /media/server ..."
I have not tested if this also appears when I am connected via ethernet.
I think it is because the 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 power-button.
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.
** Description changed:
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 :
+ I prepare for mounting with the following entry in /etc/fstab my
+ Synology NAS :
//192.168.178.61/data /media/server/server_data cifs
users,uid=1000,gid=1000,username=xxxxx,passwd=xxxxxx,iocharset=utf8,sec=ntlm,noauto,_netdev
0
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 comman "umount /media/server ..."
+ process stops at the command "umount /media/server ..."
- I have not tested if this also appears when I am connected via ethernet.
- I think it is because the Network is already disabled prior all umounts
- are done.
+ 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 power-button.
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.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1577885
Title:
120sec delay during shutdown or reboot with still mounted cifs (via
Wifi)
Status in systemd package in Ubuntu:
New
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 :
//192.168.178.61/data /media/server/server_data cifs
users,uid=1000,gid=1000,username=xxxxx,passwd=xxxxxx,iocharset=utf8,sec=ntlm,noauto,_netdev
0
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
power-button.
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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577885/+subscriptions
More information about the foundations-bugs
mailing list