Bug 623193

Summary: network manager startup delay with network mounts
Product: [openSUSE] openSUSE 11.4 Reporter: tim draper <veehexx>
Component: NetworkAssignee: Mu Lei <rlmu>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P3 - Medium CC: branislav.klocok, dmitry, forgotten_dr8e_4-OWI, harmie, Larry.Finger, muaddeep, ohering, rainer.klier, smaug42, steffeneibicht, tilman.vogel
Version: Final   
Target Milestone: Final   
Hardware: x86-64   
OS: openSUSE 11.4   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description tim draper 2010-07-17 08:39:42 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6

when having network mount points in fstab (NFS in this case), then network manager takes a long time to start itself on a freshboot/reboot of oSUSE.

problem is not present when the nfs mounts are not in fstab (ie: default fstab entries), OR if you enable 'traditional IFUP' method in Network Settings.

when NFS mounts are in fstab, and using 'networkmanager' to manage the network, the network does come up when a timeout occurs (nfs mount timeout?) so it can proceed to bring up the network stack.

my fstab entry for nfs:
192.168.0.253:/media /mnt/nas1_media nfs rsize=8192,wsize=8192,timeo=14,intr 0 0

i am on a laptop and the above occurs on both wlan and lan connections

Reproducible: Always

Steps to Reproduce:
1. enter NFS share into fstab
2. have Network Settings in it's default mode (User controlled with NetworkManager)
3. cold boot/reboot openSUSE so fstab is parsed
Actual Results:  
delay in network startup (no internet access) of upto around 5minutes, while nfs times out due to no network

Expected Results:  
instant network access within seconds of logging in.
Comment 2 Vasiliy Litovchenko 2010-07-20 07:39:46 UTC
Default boot sequence there is:
/etc/init.d/network -> /etc/init.d/nfs -> /etc/init.d/network-remotefs

If NetworkManager is used, as per to comments in /etc/init.d/network, NetworkManager is starting in network-remotefs. So first we are trying to mount nfs shares, and just after that bringing up network connection with network manager.

I'm not familiar with openSuSE boot process, so probably I did smth wrong, for now I've:
1. moved /etc/init.d/rc5.d/S05nfs to S08nfs
2. changed dependencies in /etc/init.d/.depend.start:

vasiliy@linux-0un3:/etc/init.d> diff .depend.start .depend.start.bak
9c9
< nfs: rpcbind network network-remotefs
---
> nfs: rpcbind network
16c16
< network-remotefs: cifs network
---
> network-remotefs: nfs cifs network

this works for me, at least as temporary fix, not sure if that's 100% correct.
Comment 3 Bin Li 2010-08-11 10:01:09 UTC
Hongdan,

 Could you help me take care of this issue?
Comment 4 Bin Li 2010-08-12 07:09:28 UTC
*** Bug 630261 has been marked as a duplicate of this bug. ***
Comment 5 Larry Finger 2010-08-15 18:13:27 UTC
I had the problem when using wireless. At the time that /etc/init.d/nfs is called, only a wired connection will have been established. Issuing the 'mount -a' command causes the computer to hang for 3 minutes. I "fixed" the problem by doing the mounts in the background with the following patch:

Index: init.d/nfs
===================================================================
--- init.d.orig/nfs
+++ init.d/nfs
@@ -235,7 +235,7 @@ case "$1-$nfs" in
            # as if there are 'bg' mounts, we could get multiple copies
            # of them.  So always 'settle' if there is any mounting to do.
            udevadm settle
-            mount -at nfs,nfs4 > /dev/null 2>&1
+            mount -at nfs,nfs4 > /dev/null 2>&1 &
        fi
        #
        # generate new list of available shared libraries

I do not understand the comment just above the line that changed. How is it possible to get multiple mounts running? If you do, what is the harm?

Larry
Comment 6 Dmitry Roshchin 2010-09-01 15:06:43 UTC
The reason of this bug is known, so can we expect bugfixes in Update repository?
Comment 7 Dmitry Roshchin 2010-09-25 19:55:05 UTC
(In reply to comment #2)
> 1. moved /etc/init.d/rc5.d/S05nfs to S08nfs
In openSUSE 11.3 numbers in file names doesn't matter, only ".depends.start" and ".depends.stop".

> < network-remotefs: cifs network
> ---
> > network-remotefs: nfs cifs network
I think it's bad idea. We must change only nfs start dependencies.
Comment 8 Bin Li 2010-11-05 03:17:45 UTC
*** Bug 648412 has been marked as a duplicate of this bug. ***
Comment 9 Bin Li 2011-03-17 03:42:27 UTC
*** Bug 675261 has been marked as a duplicate of this bug. ***
Comment 10 Clayton smaug42 2011-03-30 19:43:08 UTC
This is still an issue on openSUSE 11.4.
Comment 11 Forgotten User dr8e_4-OWI 2011-08-03 22:13:02 UTC
I have a problem with the network card (Realtek RTL8111/8168B PCI Express Gigabit) setup. Back at 11.2 and 11.3, it required setting up a bridge so there were two listings in the hardware setup in Yast. Now, with 11.4, I can set up eth0 and eth1, but can't do a bridge, and can never get nfs to talk to the other system (11.2). Everything in my setup is identical to what it was in from 10.x and then with the bridge, thru 11.3. 11.4 never works for nfs.
Comment 12 Branislav Klocok 2011-08-08 21:34:17 UTC
Hello Guys, it August and this bug is still here. It is very annoying. Please try to do something with this.

A lot of people are working with NFS shares and not many have the ability to change the start sequence of services.

Thanks.
Comment 13 Rainer Klier 2011-08-09 07:05:09 UTC
maybe my workaround from bug #487190 can help.
as you can read there in comment 9, i made a dispatcher scripts for networkmanager, which starts network services like nfs and smbfs AFTER networkmanager has established connection.
and i disabled all network service scripts in /etc/init.d/rc3.d and  /etc/init.d/rc5.d.
Comment 14 Bin Li 2011-08-09 16:56:55 UTC
Yes, I'll find some time to build the patch for this issue. But now I'm on vocation, maybe later. Thanks!
Comment 15 Steffen Eibicht 2011-10-20 01:45:45 UTC
Hi folks,

now we have middle of october 2011 and this bug still exists in openSUSE 11.4. In my case it seems that it is even worse, as NFS kills the whole network connection via KDE Networkmanager. KNetworkmanager can not establish a WLAN connection anymore, after you set the NFS client as active and do a reboot at some time. Version of KDE: 4.6.5 and the system is patched to the latest level.
I also noticed the same behaviour on openSUSE 11.4 with KDE 4.7.2 

please please fix it. I don´t wanna run around with USB sticks anymore :-)
Comment 17 Tomáš Chvátal 2017-08-12 09:17:56 UTC
11.4 is out of support scope. As the init scripts were redone to systemd units it is not possible to reproduce this anymore.

Please open a new issue if it is still reproducible on current releases.