NFS and FC16 and systemd

lensman3 · #1 11th November 2011, 11:20 PM

Appears to be a slight race condition with NFS starting and a machine that uses DHCP. NFS hangs because the network is not hooked up. Evenually nfs times out and the boot finishes.

Mount of the nfs volume is being done through fstab. (Worked fine in FC15).

I have in the past used a static IP and now the network manager won't let me change it because the tab is grayed out.

Any ideas?

***DBelton*** · #2 12th November 2011, 12:51 AM

Are you using network manager?

If so, try telling systemd to wait on network manager to come up and settle before starting the other services.

Code:

systemctl enable NetworkManager-wait-online.service

lensman3 · #3 13th November 2011, 05:19 AM

Yes. I'm running network manager. I edited my /etc/sysconfig/network-scripts/ifcfg-p21p1 (in my case) so that it had:

IPADDR0=192.168.200.10
PREFIX0=24
GATEWAY0=192.168.200.1
DNS1=192.168.200.1
DOMAIN=bp (YES bp, since bp is illegal and a properly configured router will drop bp)

and commented out the PEERDNS and PEERFOUTES which I think are getting set by DHCP.

So I'll see if this works. A restart of /etc/init.d/network did give me the correct static IP.

I also implmented your suggest of systemctl and noticed that the symbolic link was created.

---------- Post added at 10:19 PM ---------- Previous post was at 10:09 PM ----------

That seemed to work. At about 20 seconds the network devices was started and about 30 seconds into the boot, the network had in static IP "installed" and at 40 seconds nfs was started. There were several messages during the boot the nfs was being deferred.

Seems to me in the nfs install, the systemctl command you suggested should be automatically installed. This would at least ensure that the network is ready when NFS is activated.

***DBelton*** · #4 13th November 2011, 06:01 AM

It's been a problem with systemd and network manager for quite awhile now. I'm not sure which one is actually at fault, though.

And it's not just nfs that is affected. It's just about all network mounts, cifs as well as nfs.

Basically enabling the NetworkManager-wait-online.service is a kludge at best, but it's been the only way I could consistently get my nfs mounts to work with network manager (You still have to make sure that network manager is setup to enable your connection on boot and is available for all users so that it brings it up at boot time instead of waiting for a user to log in).

Oh, and I assume that you have already figured out that the nfs server has changed in F16? You now need to enable nfs-server.service

dragon1976 · #5 15th March 2012, 01:58 AM

NFS in my experience is the most dependable file sharing for automounting folders & directories. When begining Fedora 16, it was quite a challenge until I discovered that NFS ,like many other cifs now depend on systemd........which is a great system once you become familiar with it . The 3.0 kernel sure has changed the rules for administrators & hobbiest alike. I found your page quite helpful. My question is can NFS be provided on a domain name service in order to share directories online?