Red Hat Bugzilla – Bug 484468
NetworkManager's position in the boot order should be after nfs in order to be able to mount nfs shares
Last modified: 2009-02-13 09:58:54 EST
Description of problem:
I have an nfs share from a machine in the local network added to /etc/fstab. The setup works fine, but booting is greatly slowed due to a long wait while the system tries to mount the NFS share automatically.
The relevant line from fstab:
10.10.0.200:/data /remote/tikkulehema-data nfs ro 0 0
Version-Release number of selected component (if applicable):
Happens on every boot
Steps to Reproduce:
1. Install a default Fedora installation.
2. Have an nfs share available and try to add it to /etc/fstab
3. Boot the computer
1) The system tries to mount the share while booting, but fails after trying for a while.
2) The share is mounted and available after boot, though, when NetworkManager is brought up later in the boot process.
The long wait and fail does not happen.
Bill: whee! boot order again... thoughts?
Eh... for some reason, I wrote the title totally wrong. Of course NM should be running _before_ the shares are mounted, not after. Currently it seems that NM is started only after mounting nfs shares.
This is what the netfs NM dispatcher script is for.
Do you have both the network and NetworkManager service enabled?
Yes, I do have them both running. The secondary network card is under the traditional network service, because I need to associate the interface with a bridge.
OK, this isn't fixable for that case. The netfs script is coded to only start on boot if one of network or NM is already running - since one of them is, it's going to try to mount.
If you were only running NM for all your interfaces, or only running network for all your interfaces, it should work OK as-is.