[Pkg-utopia-maintainers] Bug#641894: Some more input

[Peter Mueller]

Hi All,

I'm observing the same issue on my machine which is a Debian 8, 64 Bits.

Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08)
x86_64 GNU/Linux

General Setup to reproduce the issue: 

I do mount a nfs file share with autofs by using the config files
auto.master and auto.nfs. (Which is a quite common setup.)

Network comes from WLAN and the Network manager

$ mount
gives 
..
server:/somefolder on /nfs/somefolder type nfs
(rw,nosuid,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,soft,
proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.xx.xx,
mountvers=3,mountport=55197,mountproto=udp,local_lock=none,addr=192.168.xx.xx)

Test:

I'm assuming the shutdown process (set to runlevel 0) calls from 

/etc/rc0.d/K04umountnfs.sh (softlink)

the script

# /etc/init.d/umountnfs.sh stop


But this does not remove the mounted folder.

So if you test as root

# /etc/init.d/umountnfs.sh 

 the mounted folder disappears (check with $mount)

but with 

# /etc/init.d/umountnfs.sh stop

the mounted folder still exists.

So the used option "stop" prevents from unmounting the nfs shared
folder.

I would assume that the shutdown process may dislike this and runs into
a timeout to disconnect from the nfs share. 

Therefore the shutdown process takes so long.

Maybe I'm wrong. 

But if not the ticked severity and the related package should be
changed.

Further investigations:

To my impression the script

/lib/lsb/init-functions

behaves different if the option "stop" is set or not. But I think there
are other Linux fellows that may know and understand this process much
better than me.

Best regards

peter