NFS dont automatically mount in Fedora 20

darwall · 04-25-2014, 05:34 AM

Hi all!
I have a problem after upgrading from Feora 19 to Fedora 20.
I have a home-network with a centos 6.4 server and NFS sharing on the /home folder and a few Fedora clients with LXDE desktop enviroment,
I am currently upgrading clients from fedora 19 to fedora 20, but have discovered that the NFS mount is not working automatically.
it simply doesnt mount anymore.
I have to type mount -a in the terminal and then it works.
The next time I start up the computer I have to type mount -a again.
I have upgraded two clients to Fedora 20 so far and itś the same problem with both.
One a computer has still Fedora 19, there is no problem. It mounts automatically.

I would be greatful if anyone have an idea

Sven from Sweden

suicidaleggroll · 04-26-2014, 09:38 AM

Have you checked the startup log, eg: /var/log/messages?

My guess is the machine is attempting to mount the NFS before it brings up its own network. The mount errors out since it can't access the NFS server, and then it continues without it.

lleb · 04-27-2014, 12:20 PM

how do you currently have the NFS share mounting on the F20 systems? sounds like the filesystem is coming alive before the network is. thus your shared connection is failing.

you might looking into moving the mount out of fstab and into autofs for now.

darwall · 04-30-2014, 05:38 PM

Quote:

Originally Posted by suicidaleggroll

Have you checked the startup log, eg: /var/log/messages?

My guess is the machine is attempting to mount the NFS before it brings up its own network. The mount errors out since it can't access the NFS server, and then it continues without it.

Hi and thanks for your reply.
There is no /var/log/messages in Fedora 20
(but there is in Fedora 19 )
I think you're right. He runs fstab before he has had time to connect with the NFS-server.
I would need to arrange some delay before mounting the NFS-server.
But I do not know how to do it. Maybe I could use the sleep command somehow?
I would really appreciate a good tip.
Sven from Sweden

suicidaleggroll · 04-30-2014, 05:52 PM

I'm not familiar enough with F20 to suggest a solid fix, but one alternative would be to write a startup script in init.d that simply runs "mount -a" to bring up any NFS mounts that failed on the first go-around.

custangro · 04-30-2014, 08:16 PM

Did you try adding _netdev in /etc/fstab?

darwall · 05-01-2014, 07:35 AM

Quote:

Originally Posted by custangro

Did you try adding _netdev in /etc/fstab?

Hello custangro!
I'm not familiar with _netdev ?
Can you give me an example how to use it?
Here below is my fstab
My servername is cos6 ( centos 6 )
Thanks
Sven from Sweden

/dev/mapper/fedora-root / ext4 defaults 1 1
UUID=ebbe2127-7750-4790-9963-324ae54c9949 /boot ext4 defaults 1 2
/dev/mapper/fedora-home /home ext4 defaults 1 2
/dev/mapper/fedora-swap swap swap defaults 0 0
cos6:/home /home nfs4 rsize=8192,wsize=8192,timeo=14,intr 0 0

custangro · 05-01-2014, 02:15 PM

Something like this

Code:

cos6:/home /home nfs4 _netdev,rsize=8192,wsize=8192,timeo=14,intr 0 0

From the mount man page

Quote:

_netdev
The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system).