[Bug 606969] New: Mounting network drives leads to deadlock, slow initialization of network interface
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c0 Summary: Mounting network drives leads to deadlock, slow initialization of network interface Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: marc@marcchamberlin.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729) It appears that there is a deadlock that is resolved by a slow timeout when attempting to mount a network drive via fstab. On my server I use fstab to mount a NAS multi terabyte disk drive. It appears that the network name for the device cannot be resolved until other services such as DHCP and Named become active. This leads to a deadlock that fails to allow the network daemon to initialize the interface (in my case eth1, my second NIC) until the initial attempt to mount the network drive times out. That slow initialization of eth1 can lead to other failures downstream such as preventing my Bacula backup daemon from automaticlly starting up as well... See my discussion on the openSuSE newsgroup - opensuse@opensuse.org started April 25, 2010, under the thread - "Slow startup of network interface" for further details. Reproducible: Always Steps to Reproduce: 1. add a networked mount in fstab 2. boot up system 3. determine when the interface for that network is actually initialized. Actual Results: Network drive is never mounted automatically... Network interface card is initialized only after a long timeout occurs from the failed attempt to mount the network drive Expected Results: I expect the network card to initialize promptly during boot up. I also expect the network drive to be properly mounted. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |puzel@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c Petr Uzel <puzel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED Severity|Normal |Major -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c1 Petr Uzel <puzel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |marc@marcchamberlin.com --- Comment #1 from Petr Uzel <puzel@novell.com> 2010-06-01 11:48:23 UTC --- Marc, I think the scenario might be as follows: - networking tries to initialize your NICs, however eth1 -for some reason- isn't initialized until the WAIT_FOR_INTERFACES (which defaults to 30s) timeout is reached - nfs initscript is run without eth1 being initialized -> fail How is eth1 initialized? DHCP? Next, could you please: 1) provide your /etc/fstab 2) set RUN_PARALLEL="no" and WAIT_FOR_INTERFACES to some higher value (300) and check if it helps (I presume 300s is enough for eth1 to get configured). Thanks -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c2 --- Comment #2 from Petr Uzel <puzel@novell.com> 2010-06-01 11:49:57 UTC --- (In reply to comment #1)
2) set RUN_PARALLEL="no" and WAIT_FOR_INTERFACES to some higher value (300) and check if it helps (I presume 300s is enough for eth1 to get configured).
Please also make sure that you have eth1 in MANDATORY_DEVICES (/etc/sysconfig/network/config). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c3 --- Comment #3 from Petr Uzel <puzel@novell.com> 2010-06-18 15:22:32 UTC --- (In reply to comment #1)
How is eth1 initialized? DHCP?
Next, could you please: 1) provide your /etc/fstab
2) set RUN_PARALLEL="no" and WAIT_FOR_INTERFACES to some higher value (300) and check if it helps (I presume 300s is enough for eth1 to get configured).
Marc: ping ^^^ -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c4 Marc Chamberlin <marc@marcchamberlin.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|marc@marcchamberlin.com | --- Comment #4 from Marc Chamberlin <marc@marcchamberlin.com> 2010-06-20 18:18:27 UTC --- Created an attachment (id=370369) --> (http://bugzilla.novell.com/attachment.cgi?id=370369) fstab file -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c5 --- Comment #5 from Marc Chamberlin <marc@marcchamberlin.com> 2010-06-20 19:15:04 UTC --- (In reply to comment #3)
(In reply to comment #1)
How is eth1 initialized? DHCP?
Next, could you please: 1) provide your /etc/fstab
2) set RUN_PARALLEL="no" and WAIT_FOR_INTERFACES to some higher value (300) and check if it helps (I presume 300s is enough for eth1 to get configured).
Marc: ping ^^^
Eth1 is initialized statically to an IP address of 192.168.2.100 An additional FYI, I am mounting a network drive - named //teraserver and it does require the DHCP server to be running in order to assign it it's IP address. As you read the rest of my report, keep this in mind as I think it may be part of the issue since it is critical that this be mounted for my bacula backup server. I have attached a copy of my fstab file with some sensitive info remove. In the meantime, I have come up with a partial workaround that improves things a bit, but I am still experiencing a slow initialization of eth1 (not as slow) For the workaround I commented out the mount of the network drive - teraserver and use an autofs mount instead. I tested your suggestions, with RUN_PARALLEL="no" in the /etc/sysconfig/boot file and WAIT_FOR_INTERFACES="300" in the /etc/sysconfig/network/config file, removed the autofs mount for my terastation network drive and configured fstab to mount it instead. This resulted in a very long pause during the boot up of about 5 minutes when eth1 was being initialized. Once past that pause, most of my other services came up ok, except I run bacula which is dependent upon the //teraserver/share being mounted at /data/terastation. This mount failed and when the system came up, I had to do a manual mount -a to get it mounted, then start the bacula service manually also. So I will reconfigure my system to use autofs as a workaround, but I think this problem should still be fixed and some thought given to how these services and activities be staged. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606969 http://bugzilla.novell.com/show_bug.cgi?id=606969#c6 --- Comment #6 from Marc Chamberlin <marc@marcchamberlin.com> 2010-06-20 19:19:08 UTC --- (In reply to comment #3)
(In reply to comment #1)
How is eth1 initialized? DHCP?
Next, could you please: 1) provide your /etc/fstab
2) set RUN_PARALLEL="no" and WAIT_FOR_INTERFACES to some higher value (300) and check if it helps (I presume 300s is enough for eth1 to get configured).
Marc: ping ^^^
(In reply to comment #2)
(In reply to comment #1)
2) set RUN_PARALLEL="no" and WAIT_FOR_INTERFACES to some higher value (300) and check if it helps (I presume 300s is enough for eth1 to get configured).
Please also make sure that you have eth1 in MANDATORY_DEVICES (/etc/sysconfig/network/config).
Yes, both eth0 and eth1 have been configured in MANDATORY_DEVICES -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=606969 https://bugzilla.novell.com/show_bug.cgi?id=606969#c7 Petr Uzel <puzel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #7 from Petr Uzel <puzel@novell.com> 2011-05-23 08:52:00 UTC --- I'm sorry, but 11.2 is now out of maintenance, so I'm closing this bug. Please reopen if you encounter it again in one of the supported releases. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com