Unmount of remote CIFS shares fails with timeout on system shutdown

Some more infos:
My system is Kubuntu Feisty Fawn with all present updates. I'm using a static network connection with dhcp (eth1) and I have an unused connection (on eth0).

excerpt of /etc/network/interfaces
auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

KNetworkmanager reports the dhcp configured interface as "wired online" (reverse translation from german) and the unused interface is greyed out.

When I open the "Static connections" dialog I see eth0 with an avahi-ip (169.-range) and eth1 with a valid IP adress (from the dhcp server)

That means everything is looking fine. Networking is all as it should be with and without NetworkManager running. The only glitch I have with nm is the umount problem on system shutdown.

I can confirm this bug. I've experienced it on a couple of systems - one running Feisty and one running Dapper. Both of these have network-manager installed. Several other systems, running Edgy, and _without_ network-manager installed, don't exhibit this problem.

The result (for me) is that the system fails to complete shutdown and I have to power off or reset manually.

Unlike the bug reporter I'm not mounting the CIFS shares on system startup - they are mounted manually - so that's not part of the problem.

I don't currently have a system running Edgy _with_ network-manager, but if I do have reason to set one up I'll report what I find.

Andy B

I have the same problem here with a Feisty-machine with auto-mounted CIFS filesystem.
The reason for this seems to be that dbus, which controls NetworkManager is shut down at /etc/rc0.d/K20dbus which is run before /etc/rc0.d/S31umountnfs.sh

I also have this problem on Ubuntu Feisty.

I have exactly the same problem on Ubuntu Feisty. I my case, also I get messages during shutdown complaining about CIFS command timeouts (CIFS shares are mounted on bootup from /etc/fstab).

I can also confirm that after removing the network-manager package the problem completely disappears.

I experience the same problem, both previously with Edgy, and now with Feisty. My CIFS shares are not mounted at boot time, but rather manually.

The computer does eventually shut down, but it hangs for a minute or two on each share. It displays a timeout error message for each share (this is in text mode, after X has already shut down).

I can confirm this bug on Feisty.

It gives following error message after shutdown and hangs for a few minutes:

[5445.206278] CIFS: server not responding
[5455.206325] CIFS: No response for cmd 50 mid 609

It seems the CIFS umount hangups happen when rc6.d/S20sendsigs is run, I changed this link to S45sendsigs, and the system unmounts remote file systems successfully before rebooting. On my Ubuntu Feisty install, K20dbus exists only in rc1.d/ which doesn't get run when shutdown is called with reboot.

I can confirm that the above fixes the problem on my Feisty system; though I had to do the same (mv S20sendsigs S45sendsigs) in /etc/rc0.d as well, to have it work when shutting down the system instead of just rebooting. I don't know if it's the correct way, but thanks to ardya anyway for the workaround.

Actually, it turns out that moving S20sendsigs to S45sendsigs is not a right idea because it somehow breaks the functionality of the following scripts on my second Feisty installation. Moving S31umountnfs.sh to S17umountnfs.sh seems to work better. The description in S15wpa-ifupdown says that it goes before sendsigs because sendsigs kills something it needs; in our case sendsigs must be killing network-manager which shuts down network interfaces which makes it impossible for CIFS to unmount its file systems properly.

I can also confirm this bug. I upgraded seven machines from Edgy to Feisty today and now they all show these CIFS VFS errors on shutdown. After some timeout they all continue the shutdown process. Not a showstopper, but definitely a bug.

I'm assuming wpa is wireless related, since I don't use that I wasn't aware, good eye dmik.

As further practice has shown, umountnfs.sh should be moved up more, so that it runs before K20dbus (isn't network-service actually a dbus-based service and therefore gets terminated when dbus shuts down?). For example, to K17umountnfs.sh. When placed there, SMB/CIFS shares are unmounted before the network is down as a result of network-service termination. The only situation where I still get the described delay is if I shutdown/reboot my PC too quickly after starting it up -- in particular, before an attempt to auto-mount an inaccessible SMB/CIFS share from fstab is timed out. In this case, umountnfs.sh does nothing (since the share isn't mounted yet), which leads to a complain from CIFS still trying to find a network resource when the network gets down.

Anyway, all this is just tossing things around again. I have no real knowledge about System V init and Debian specifics, so I may be wrong somewhere.

The following link seems to have a good handle on the problem. A fix is also included.

http://www.jejik.com/articles/2007/07/automatically_mounting_and_unmounting_samba_windows_shares_with_cifs/

Has anyone had a chance to test for this on Gutsy?

Yes - and it's still present.

Andy

On Sat, Sep 01, 2007 at 10:18:34PM -0000, Andy Bovett wrote:
> Yes - and it's still present.
>
> Andy
>

The bug this is a duplicate of is called: "network manager should not ifdown interfaces
when stopped" ... or something like that. Launchpad appears to be
down, so I cannot search and mark this accordingly ...

 - Alexander

The bug Alexander Sack is referring to is: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/128316

Another bug report that seems to be the same is:
https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/24330

I also had this problem on Feisty, both with mounting automatically and mounting manually. I've upgraded to Gutsy, and I still have this problem.

cyli, thanks for the bug id.

Can you please test latest network-manager? 0.6.5-0ubuntu13.

Thanks,
 - Alexander

I can confirm, latest Gutsy (Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux) this problem still persist.

In http://ubuntuforums.org/showthread.php?t=288534 Mr. Max.Durden has created a patch. Could this be applied to the official release?

Sorry, just a "me too" here:

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

date
Wed Jan 2 19:31:25 CET 2008

Same problem: long timeout, displayed complaint about CIFS (dont have the exact one here) then the system shuts down. I'll be looking into the suggested fixes, thanks for those DrCore, Philippe Clérié, Dmik et al!
And good luck (and happy new year ;) to all the dev's and users who keep on working to make ubuntu perfect!

The bug is still present in 8.04LTS Hardy Heron.

This fix: http://blog.avirtualhome.com/2008/03/10/ubuntu-shutdown-problem-cifs-related/ (reported in https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/42121) works fine for me on 8.04LTS Hardy.

Yes I know, i read a quick fix replacing order in rc and it works like a
charm, don't know why it wans't included being so easy

On Fri, May 2, 2008 at 6:58 AM, Jerry West <email address hidden> wrote:

> *** This bug is a duplicate of bug 42121 ***
> https://bugs.launchpad.net/bugs/42121
>
> The bug is still present in 8.04LTS Hardy Heron.
>
> This fix: http://blog.avirtualhome.com/2008/03/10/ubuntu-shutdown-
> problem-cifs-related/<http://blog.avirtualhome.com/2008/03/10/ubuntu-shutdown-problem-cifs-related/> (reported in
> https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/42121) works
> fine for me on 8.04LTS Hardy.
>
> --
> Unmount of remote CIFS shares fails with timeout on system shutdown
> https://bugs.launchpad.net/bugs/90795
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 42121).
>

This is present in Intrepid as well..

Description: Ubuntu intrepid (development branch)
Release: 8.10

I mount several shares from a Win2k3-R2 server using CIFS via fstab. Of course, if i manually unmount them before shutdown/reboot, this problem goes away.

network-manager:
  Installed: 0.7~~svn20081015t224738-0ubuntu1
  Candidate: 0.7~~svn20081015t224738-0ubuntu1
  Version table:
 *** 0.7~~svn20081015t224738-0ubuntu1 0
        500 http://ca.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Why is this marked as a duplicate? The bug marked as "original" doesn't describe the same problem or am I wrong? At any rate, this is still a problem even in Jaunty!