Mageia forum

I have been using NFS in Linux for quite a while, but this is my first implementation of NFS mount points in Mageia 4, so forgive my posting, as I am trying to resolve the NFS issue as well as examining the potential for autofs.

My mount point is intended to provide resources to to all of the servers. My fstab entry is:

192.168.50.15:/sysadm /sysadm nfs rw,hard,intr 0 0

This is currently in place with other servers, and the connection is stable and reliable. However, when I attempt to connect via Mageia 4, I am greeted with the following:

mount -a
mount: none is already mounted or /proc busy
none is already mounted on /tmpfs
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

What am I doing wrong? Is there something that is missing from my installation?

Thank you.

For one, please don't use mount -a if you only want to mount /sysadm. Second, please show only the output of

Code: Select all

mount -v /sysadm

Did you start any NFS services via systemctl on the client yet?

No,I cannot remember having to do that before.

Code: Select all

rpm -qa | grep nfs
nfs-utils-1.2.8-2.mga4
libnfsidmap-doc-0.25-5.mga4
lib64nfsidmap0-0.25-5.mga4
unfs3-0.9.22-5.mga4

Where is it?

As odd as it sounds, I was having problems with rpcbind as discussed in this thread: viewtopic.php?f=7&t=8839&p=54060&hilit=privoxy&sid=df02c95b81f398d696737403b21f8a6e#p54060

The problem was systemd screwing up apparently because of a problem with my nvidia driver, and I apparently solved the problem with a change in version of the driver. Solving the problem I was having (with TTYs) also solved the problem with rpcbind.

Something for you to look at, even though superficially they would look unrelated.

Well it certainly would make sense that systemd was messaing with rpcbind. I will investigate that further. I have serious 64-bit issues, which are not on the 32-bit platform.