Having problems mounting an NFS share

[kabads]

My raspberry pi arch linux is running a client NFS, and I have another couple of arch linux machines which connect quite happily to a NFS share. However, the arch linux arm version is having a problem. I'm getting:

$this->bbcode_second_pass_code('', '[adam@atomic ~]$ sudo mount -t nfs 192.168.1.156:/srv/nfs4/video /home/adam/disk3
mount.nfs: an incorrect mount option was specified')

I've tried looking at everything, but the NFS server is coping with other clients - just the arch linux arm machine can't mount it. Any suggestions where I should look?

[moonman]

Have you read https://wiki.archlinux.org/index.php/NF ... l_mounting ?

[kabads]

I have, and that is how I have set up the other machines. I've followed all the steps and until a week ago, it was working on the arm machine. It's tricky working out what changed since then, to cause it not to work.

[hp4]

I've the same problems on my Raspberyy Pi since the last system update. One of the updated packages was

nfs-utils 1.3.2-3

I've fount a hint

https://bbs.archlinux.org/viewtopic.php?id=183444

that this could be responsible for the problems. I reinstalled and activated all the services mentioned in this hint (rpc-bind...) but without success!!

Running the mount command with the -v option yields the output shown below. It indicates some inconsistencies in the package versions. But Since I'm not an export for network-software I'm not able to fix this.

Any idea how to procedd?


--------------------------------------------------------------------------------------------------
mount.nfs: prog 100003, trying vers=3065210072, prot=6
mount.nfs: trying 192.168.178.3 prog 100003 vers 3065210072 prot TCP port 2049
mount.nfs: portmap query retrying: RPC: Program/version mismatch
mount.nfs: prog 100003, trying vers=3065210072, prot=17
mount.nfs: trying 192.168.178.3 prog 100003 vers 3065210072 prot UDP port 2049
mount.nfs: portmap query failed: RPC: Program/version mismatch
mount.nfs: Protocol not supported
--------------------------------------------------------------------------------------------------

[hp4]

rollback to

nfs-utils-1.3.1-1

solved my problem!

[kabads]

I'm not familiar with roll-backs, but will give it a go. Can you put the package on hold so that you can run an update each time with that package frozen?

[moonman]

You might need to specify nfs version now if you are using v3 as v4 has become the default recently.

[kabads]

I tried specifying -t nfs4 with mount, but still no joy.

A downgrade to 1.3.1 worked and then I've just put IgnorePkg = nfs-utils in /etc/pacman.conf to stop the upgrade with next pacman -Syu

All working with older package -not sure how long a newer one will be - do they need a bug being created upstream?