CIFS mounts are unmounted after disabling network

[Jacco van Koll]

Whenever a CIFS is mounted remote, this will not be unmounted before the network-interfaces are brought down. Therefor, a long timeout exists whenever a system is going to shutdown or reboot.
Request: Please unmount remote filesystems before disabling network connectivity.

Used version: Ubuntu Hardy 64bit, standard package kernel and initscripts

[Adrián Santos Marrero (lagoon)]

My CIFS mounts refuses to umount when I halt o reboot the system. It seems that a script is stopping the network before the call of /etc/rc[06].d/S31umountnfs.sh.

I'm using Kubuntu 7.10 64bits.

Thank you in advance.

[Borahshadow (codyregister)]

I too seem to have this problem running kubuntu 7.10 32bit

[Scott James Remnant (Canonical) (canonical-scott)]

Not an Upstart problem, leave open on SysVinit

[sam fielder (srf10130)]

same here on hardy 64.

rc6 and rc0 both have umountnfs listed at S31 and wpa-ifupdown at S15.

this causes the network interface to drop before remote filesystems are umounted.

manually renaming /etc/rc0.d/S31umountnfs.sh and /etc/rc6.d/S31umountnfs.sh to S14umountnfs.sh seems to solve the problem.

[Jacco van Koll (jko-deactivatedaccount)]

Tried that, and fixed the issue!

On 20-04-08 16:10, sam fielder wrote:
> same here on hardy 64.
>
> rc6 and rc0 both have umountnfs listed at S31 and wpa-ifupdown at S15.
>
> this causes the network interface to drop before remote filesystems are
> umounted.
>
> manually renaming /etc/rc0.d/S31umountnfs.sh and
> /etc/rc6.d/S31umountnfs.sh to S14umountnfs.sh seems to solve the
> problem.
>
>

--
Regards,

Jacco van Koll

<email address hidden>

[MichaelE (michael-eitelwein)]

Can confirm the bug on a desktop (8.04 64bit) and laptop (8.04 32bit). Both are upgrades from 7.10. The workaround above solved the problem for me.

Another laptp with a fresh installation of 8.04 release candidate shows the same problem: S31umountnfs.sh and S15wpa-ifupdown.

Would not adding the right dependency (network?) to /etc/init.d/umountnfs.sh finally solve the problem?

[luchio (luch3)]

> manually renaming /etc/rc0.d/S31umountnfs.sh and
> /etc/rc6.d/S31umountnfs.sh to S14umountnfs.sh seems to solve the
> problem.

This fix works, I would like to nominate this for a release.

Fix:
mv /etc/rc0.d/S31umountnfs.sh /etc/rc0.d/S14umountnfs.sh
mv /etc/rc6.d/S31umountnfs.sh /etc/rc6.d/S14umountnfs.sh

[flaccid (chris-xhost)]

From memory there are duplicates of this bug.

Can one of the suitable fixes be released in updates and also Intrepid?

I really don't want to see this bug raise its head again...

[flaccid (chris-xhost)]

Its been 10months which is nearly 2 release cycles and still no completion. This makes us look pretty amateurish.

Surely someone subscribed here can sponsor and commit this fix.