fedora 17 cannot mount nfs shares using fstab

[johndoe1000]

hi,
i have installed a fresh fedora 17.
i want to mount nfs shares on boot using fstab.
here is a snippet from my fstab:
192.168.0.4:/Pictures /home/george/Pictures nfs _netdev 0 0

I have enabled the network manager wait service:
systemctl enable NetworkManager-wait-online.service

i have also increased the wait time in the service above to 60 seconds.

still it does not mount.

when looking at the /var/log/boot.log file i see error just before the mounting:
Failed to start NFS file locking service..
See 'systemctl status nfs-lock.service' for details.
[ESC[1;32m OK ESC[0m] Reached target Remote File Systems (Pre).
Mounting /home/george/Pictures...
Starting Sendmail Mail Transport Agent...
[ESC[1;31mFAILEDESC[0m] Failed to mount /home/george/Pictures.
See 'systemctl status home-george-Pictures.mount' for details.

when looking at both status files i see the same error:
rpc.statd is not running

can you please help me?

[acidzebra]

As root:
systemctl enable rpcbind.service
systemctl enable nfs-lock.service
systemctl enable nfs-idmap.service
systemctl start rpcbind.service
systemctl start nfs-idmap.service
systemctl start nfs-lock.service

then try mounting again.

[jpollard]

RPC bind is not needed on the client. And as I understand, NFSv4 doesn't require it even on the server.

Look in the /var/log/messages file and see what the real errors are. Possibly, the firewall on the server is not allowing your client to connect.

[Xavior]

Is this yet another time I have to disable seLinux ?

I can't get nfs to connect either.

~frustrated

[jpollard]

Has nothng to do with SELinux, except possibly on the server - it has to be told to permit NFS exports.

But this is the client.

Oh, and this is an old thread...

[glennzo]

This is indeed an older thread. In the spirit of helping Xavior there needs to be an exported folder on the server side. On my server I export the /script folder to all takers on my local network. In /etc/exports I add

PHP Code:

/script   10.0.0.0/24(rw,sync,no_root_squash,no_all_squash) 


Save and exit. Then

PHP Code:

systemctl enable nfs-server.service
systemctl start nfs-server.service
exportfs -rav 


Then from a client I can mount this automatically in fstab.

PHP Code:

server:/script /mnt/script nfs _netdev,auto 0 0 


There needs to be a /mnt/script folder on the client.

[Xavior]

It's about Fedora 17, nfs client not connecting, so it's relevant.
The server has not changed and was working for year before....
my client was updated ffrom F14 to F17 and now doesn't work.
$ mount /sharedir
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

and I don't think it has anything to do with statd...

Any ideas?

---------- Post added at 12:15 PM ---------- Previous post was at 12:13 PM ----------

Do I need to disable selinux again in F17 too ?

---------- Post added at 12:16 PM ---------- Previous post was at 12:15 PM ----------

...and do I need to make firewall ports static in F17 ? if so what file do I set these in it used to be /etc/sysconfig/nfs but I don't see same things anymore in that file...

~Ahhhhh!!! lol

[glennzo]

Originally Posted by Xavior

Do I need to disable selinux again in F17 too ?

On my server selinux is set to enforcing.

PHP Code:

[glenn@blackhole ~>$ getenforce
Enforcing 


To troubleshoot you could set it to permissive.

PHP Code:

setenforce 0 


[glennzo]

NFS4 should be allowed in the firewall configuration on the server.

PHP Code:

yum install system-config-firewall-tui
system-config-firewall-tui 


[Xavior]

The server is F14, and other F14 PC has no issues connecting,
so why would server that's been working for a year be the problem?

Just curious,
Xav