Arch Linux

P. Boisjoli

Member

Registered: 2018-04-12

Posts: 3

NFS mount parameter clientaddr not recognized on upgrade of nfs-utils.

After upgrading nfs-utils (2.3.2-2 -> 2.3.3-1), a mount -t nfs4 -o ...,clientaddr=192.168.132.4:4010,... now return error msg:
"mount.nfs4: an incorrect mount option was specified".

Removal of the clientaddr=... parameter mount correctly.

Problem seem upstream. Anyone can confirm this behavior before I file a bug upstream?

Also, any direction as to where to file the bug upstream would be appreciated as I'm unsure of the correct place.

Problem possibly caused by "2018-06-19 Add check of clientaddr argument" [http://git.linux-nfs.org].

loqs

Member

Registered: 2014-03-06

Posts: 17,321

Re: NFS mount parameter clientaddr not recognized on upgrade of nfs-utils.

If you use clientaddr=192.168.132.4 instead?  http://git.linux-nfs.org/?p=steved/nfs- … 5c8f2ac34c expects an address without a port.

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,597

Website

Re: NFS mount parameter clientaddr not recognized on upgrade of nfs-utils.

Is there a reason why you're adding all those mount options?  On my NFS share:

# mount nas.lan:/scratch /scratch
# mount grep nas
nas.lan:/scratch on /scratch type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.1.10.108,local_lock=none,addr=10.9.8.228)

---

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

P. Boisjoli

Member

Registered: 2018-04-12

Posts: 3

Re: NFS mount parameter clientaddr not recognized on upgrade of nfs-utils.

@loqs:
Without specifying the port, only the address, the mount work. It seem 2018-06-19 mod implement now strict IP specification w/o port. Very bad since I was using this mechanism to direct callback to a fixed port for firewalling. Since man page do not explicitly indicate allowance for IP:port it is not a bug.

@graysky:
The server only support NSFv4.0, so cannot implement callback thru same client TCP connection like NFSv4.1 or 4.2. Upgrade to server won't occur before some times. Fixed callback port is required for iptables.

Me think only solution is a downgrade to nfs-utils v2.3.2-2.

Thanks all.

ETA:
Seem better to keep upgraded nfs-utils and specify callback port in /etc/modprobe.d/nfs.conf using:
## Static ports for NFS Callback
options nfs callback_tcpport=4010

Sorry for my confusion.

Last edited by P. Boisjoli (2018-09-15 19:56:05)