https://bugzilla.novell.com/show_bug.cgi?id=410428 Robert Vojcik changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |snwint@novell.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 User dcollingridge@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410428#c3 --- Comment #3 from Daniel Collingridge 2008-09-24 13:40:16 MDT --- This is also a problem on SLES 11 (Beta 1). It worked fine on SLES 10 SP2. Can we get an idea as to when this might be fixed? Are there any logs that we could attach that would help diagnose the problem? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 User jdelvare@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410428#c5 --- Comment #5 from Jean Delvare 2008-09-27 14:35:49 MDT --- Oops. My problem was that package samba-client wasn't installed. After installing this package, cifs disks are mounted at boot as expected. Sorry for the noise. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |nfbrown@novell.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410428#c9 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|dcollingridge@novell.com | Resolution| |FIXED --- Comment #9 from Neil Brown 2008-10-16 23:27:04 MDT --- Closing, as this is believe to be fixed (see comment #8) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 Daniel Collingridge changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |nfbrown@novell.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 User dcollingridge@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410428#c12 Daniel Collingridge changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|dcollingridge@novell.com | --- Comment #12 from Daniel Collingridge 2008-11-07 10:15:11 MST --- Here is what is in /etc/fstab (with IPs and directories substituted): <serverIP1>:/<remoteMount1> /<localMount1> nfs auto,rw,addr=<serverIP1> 0 0 <serverIP2>:/<remoteMount2> /<localMount2> nfs auto,ro,addr=<serverIP2> 0 0 <serverIP3>:/<remoteMount3> /<localMount3> nfs auto,ro,addr=<serverIP3> 0 0 <serverIP4>:/<remoteMount4> /<localMount4> nfs auto,ro,addr=<serverIP4> 0 0 <serverIP5>:/<remoteMount5> /<localMount5> nfs auto,ro,addr=<serverIP5> 0 0 So, I have 5 nfs mounts set up, and I verified that they are all mounted before I reboot. As for the listing of the rc.d: lrwxrwxrwx 1 root root 6 2008-11-03 14:41 /etc/rc.d/rc3.d/K04nfs -> ../nfs lrwxrwxrwx 1 root root 6 2008-11-03 14:46 /etc/rc.d/rc3.d/S05nfs -> ../nfs lrwxrwxrwx 1 root root 6 2008-11-03 14:41 /etc/rc.d/rc5.d/K04nfs -> ../nfs lrwxrwxrwx 1 root root 6 2008-11-03 14:46 /etc/rc.d/rc5.d/S05nfs -> ../nfs Then I reboot. Once the machine is back up, only 1 out of the 5 NFS mounts is still mounted (the last one). All others are not mounted. The rc.d directory still shows: lrwxrwxrwx 1 root root 6 2008-11-03 14:41 /etc/rc.d/rc3.d/K04nfs -> ../nfs lrwxrwxrwx 1 root root 6 2008-11-03 14:46 /etc/rc.d/rc3.d/S05nfs -> ../nfs lrwxrwxrwx 1 root root 6 2008-11-03 14:41 /etc/rc.d/rc5.d/K04nfs -> ../nfs lrwxrwxrwx 1 root root 6 2008-11-03 14:46 /etc/rc.d/rc5.d/S05nfs -> ../nfs I have to do a "mount -a" to get the other 4 to come back online. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410428#c15 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@novell.com --- Comment #15 from Neil Brown 2008-11-10 15:50:18 MST --- Thanks for the extra detail. Yes, it does seems like a strange timing problem. That fact that 151.155.138.1 fails while 151.155.138.11 - which is presumably one the same subnet - succeeds make it look like the network suddenly becomes available between the attempts to mount the 3rd and 4th NFS filesystems. It looks like it is about 3 seconds per attempt. So somewhere around 9 seconds, the network suddenly comes up. You could explore this more by putting commands like ifconfig -a > /tmp/ifconfig-before near the start of the /etc/init.d/nfs, and ifconfig -a > /tmp/ifconfig-after towards the end (after the "mount -at nfs,nfs4"). However /etc/init.d/nfs is supposed to run after /etc/init.d/network and I'm fairly sure that it does (network is a S02network and nfs is at S05nfs). So it seems that 'network' isn't completely starting the network before it continues Maybe the problem is related to the new "network-remotefs" thing which I don't really understand yet. So: Dan: could you give some details of your network setup. What interfaces do you have? Are they configured by networkmanager or DHCP or static IPs or .... Marius: could you have a look and see if network-remotefs could in some way be causing this? 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mt@novell.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410428#c19 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |dcollingridge@novell.com --- Comment #19 from Marius Tomaschewski 2008-11-18 05:43:23 MST --- See previous comment. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410428#c21 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |dcollingridge@novell.com --- Comment #21 from Marius Tomaschewski 2008-11-18 08:44:41 MST --- See Bug #443413. Please set in ifcfg-br* files: BRIDGE_STP='off' BRIDGE_FORWARDDELAY='0' or BRIDGE_STP='on' BRIDGE_MAXAGE='4' BRIDGE_HELLOTIME='1' BRIDGE_FORWARDDELAY='4' Does it work when you set this parameters? Please test also using the most recent sysconfig package, i.e.: * SLES11/11.1: http://download.opensuse.org/repositories/home:/mtomaschewski:/Factory/openS... * 11.0: http://download.opensuse.org/repositories/home:/mtomaschewski:/11.0/openSUSE... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=410428 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410428#c23 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME --- Comment #23 from Marius Tomaschewski 2008-12-11 02:16:29 MST --- (In reply to comment #22 from Dan Collingridge)

OK, the first suggestion worked perfectly. Everything got mounted:

...

...

BRIDGE_STP='off' BRIDGE_FORWARDDELAY='0'

With the 2nd suggestion, only 3 of the 5 mounts got mounted.

...

...

BRIDGE_STP='on' BRIDGE_MAXAGE='4' BRIDGE_HELLOTIME='1' BRIDGE_FORWARDDELAY='4'

Since the first scenario worked I didn't try the most recent sysconfig packages that you listed, but I can try that if you still need me to.

No, you don't need. I think we can close it, since it is a configuration issue. YaST2 on SLES 11 should set the parameters by default. By default, a bridge is using STP with defaults from IEEE specs and needs someting like 50 secs to find shortests paths and make sure, that there are no loops in the topology. Until the procedure finished, it blocks all traffic, so dhcp client & nfs simply can't work. [See also BRIDGE HOWTO] The 2nd suggestion tweaks the parameters and gives ~12 sec takeover time. Depending on the number of interfaces and dhcp clients (that may do "rfc sleep" for 1..10 sec to "desynchronize" the start) - all together, this may still cause problems. With enabled STP it makes sense to tweak also the DHCLIENT_WAIT_AT_BOOT (how long to wait for IP from dhcp) and WAIT_FOR_INTERFACES (how long to wait for all in the network script interfaces) options. Because of the problems, sysconfig also provides the "man 5 ifservices" mechanizms, allowing you to start/stop services when the interface is ready. -- 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.