Bug 139934
Summary: | netfs fails to mount nfs file systems from /etc/fstab | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Aleksandar Milivojevic <alex> | ||||||||
Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 3 | CC: | mattdm, rvokal | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | 8.35-1 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2006-07-11 16:32:28 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 150221 | ||||||||||
Attachments: |
|
Description
Aleksandar Milivojevic
2004-11-18 20:49:18 UTC
Static IP? Both client and the server have static IP address. I'm guessing that if you add 'sleep 5' to the top of netfs, it works? Created attachment 107051 [details]
sleep 5 than nfs mount
Ah, so my great theory falls apart. Sleep 5 does the trick. Is it needed for
NFS only or for all the stuff in netfs? What I did for now was to add sleep 5
just before NFS mounts, not to slow boot process if there's no NFS mounts. As
in attached patch.
BTW, is this something specific for my installation (what? why?), or is this
generic problem?
Thanks for help.
It appears that when it tries to mount the first NFS share, it's still negotiating with the switch for link. You could concievably fix this by adding: check_link_down ${REALDEVICE} to the end of the static networking init section in ifup. Created attachment 107090 [details]
add check_link_down to ifup script
I've attempted to add check_link_down to ifup script as you suggested, and it
didn't work. I've added one debugging echo to it, and by looking in log files
after reboot, it seems that check_link_down was called only for lo interface,
but not for eth0 interface. eth0 has static IP address, so I would expect that
I added it to the right place (after line 407 in FC3 ifup script). I've
inluded the patch with changes that I made.
Created attachment 107091 [details]
fix for check_link_down
You probably need this as well.
I've tried it out, still same results (error while mounting first file system). In log files I'm seeing "waiting for link on lo" (from my patch), but not on eth0. BTW, looking at your patch, it looks mostly as different formatting? I can't find any differences in the code? In the previous version, if the link is 'UP' according to ifconfig, it skips the test entirely. Hm, even after calling check_link_down and patching network-functions, it still doesn't work. I've added some debugging, so I know that check_link_down was called for my ethernet interface. check_link_down returns indicating that link is up. However netfs still fails to mount first file system. This is how I called check_link_down: # Wait for link if check_link_down ${REALDEVICE}; then echo $" failed; no link present. Check cable?" fi (maybe this should be part of ifup anyhow, it would only print warning during boot if cable is unplugged). Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! There is NETWORKDELAY and LINKDELAY in the current development initscripts that may help to solve this for you. From sysconfig.txt: NETWORKDELAY=<delay in seconds> Delay in seconds after all network interfaces are initialized. Useful if network has spanning tree running and must wait for STP convergence. Default: 0 (no delay) LINKDELAY=<time in seconds> Time that the system should pause after the specific interface is enabled. This may be useful if one interface is connected to a switch which has spanning tree enabled and must wait for STP to converge before the interface should be considered usable. |