[Pkg-sysvinit-devel] Bug#477498: Fwd: Shutdown & Reboot scripts try umount CIFS but CIFSD is killed first

Peter Nowee peter.nowee at gmail.com
Mon Jul 14 21:40:21 UTC 2014

---------- 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


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


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
- 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?


Recent forum mentions of users running into this problem:


Debian Package Tracking System - network-manager:

More information about the Pkg-sysvinit-devel mailing list