Bug#477498: Fwd: Shutdown & Reboot scripts try umount CIFS but CIFSD is killed first

[Dmitry Bogatov]

control: tags -1 +moreinfo

Dear submitter, does bug reproduces on current system. If yes,
do you have NetworkManager installed?

[2014-07-14 23:40] Peter Nowee <peter.nowee at gmail.com>
> ---------- Forwarded message ----------
> From: Peter Nowee <peter.nowee at gmail.com>
> Date: Mon, Jul 14, 2014 at 11:38 PM
> Subject: Re: Shutdown & Reboot scripts try umount CIFS but CIFSD is killed first
> To: 477498 at bugs.debia.org, 516733 at bugs.debian.org, 431966 at bugs.debian.org
> 
> Hi,
> 
> I think this 7-year-old bug affects my fresh and up-to-date install of
> Debian Wheezy. My CPU is a AMD Athlon XP 2200+, so I'm on
> i386-architecture, not amd64. I'm running wpa_supplicant and
> NetworkManager to connect to wireless, and made an /etc/fstab entry
> for a cifs network mount. On shutdown or reboot, the system hangs for
> a long time (probably five minutes) between:
> 
> ...
> stopping enhanced syslogd: rsyslogd
> 
>   and
> 
> CIFS VFS: Server bigbee.local has not responded in 300 seconds. Reconnecting...
> ...
> 
> See links below to forum reports of other users running into this
> problem on Debian Wheezy and Ubuntu. Workarounds commonly suggested
> are:
> - Manually changing init-scripts or their priorities to ensure
> umounting before the network goes down, or
> - Avoiding the use of auto-mounted network shares, or
> - Using /etc/network/interfaces instead of NetworkManager.
> 
> In 2011, Mike Perrin on the Ubuntu bug tracker suggested this problem
> had to be solved in NetworkManager, so he filed a bug report upstream.
> His report was marked duplicate at the time, but the original bug
> (that his report was a duplicate of) was fixed last month. The fix got
> included in the recently released NetworkManager 0.9.10:
> 
> "The NetworkManager dispatcher got some enhancements too.  It now has
> a “pre-up” event that allow scripts to execute before NetworkManager
> announces connectivity to applications.  We also added a “pre-down”
> event that lets network filesystems flush data before the interface is
> actually disconnected from the network." - Dan Williams,
> NetworkManager developer, June 20, 2014.
> 
> I see that unstable currently has a package for network-manager
> 0.9.10. I'm running stable here, so I cannot check if this solves the
> problem, but perhaps someone else can?
> 
> Regards,
> Peter
> 
> Recent forum mentions of users running into this problem:
> forums.debian.net/viewtopic.php?f=5&t=70798&start=30
> forums.debian.net/viewtopic.php?f=5&t=111509
> 
> Upstream:
> bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/211631/comments/148
> https://bugzilla.gnome.org/show_bug.cgi?id=650925
> https://bugzilla.gnome.org/show_bug.cgi?id=387832
> http://blogs.gnome.org/dcbw/2014/06/20/well-build-a-dream-house-of-net/
> 
> Debian Package Tracking System - network-manager:
> https://packages.qa.debian.org/n/network-manager.html
>