FS#43742 - [nfs-utils] Unable to mount NFS shares after latest package update.
Attached to Project:
Arch Linux
Opened by Dustin Falgout (lots0logs) - Sunday, 08 February 2015, 18:57 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 24 February 2015, 07:43 GMT
Opened by Dustin Falgout (lots0logs) - Sunday, 08 February 2015, 18:57 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 24 February 2015, 07:43 GMT
|
Details
Description: After latest update NFS mounts fail to mount.
The issue does not occur after downgrading to the previous
version.
Additional info: Version that is broken: 1.3.2-3 Version that works: 1.3.1-1 Steps to reproduce: Try to mount an NFS share. The following error shows in the journal: rpc.statd[4913]: Version 1.3.1 starting rpc.statd[4913]: Flags: TI-RPC rpc.statd[4913]: Running as root. chown /var/lib/nfs to choose different user rpc.statd[4913]: failed to create RPC listeners, exiting systemd[1]: rpc-statd.service: control process exited, code=exited status=1 systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. systemd[1]: Unit rpc-statd.service entered failed state. systemd[1]: rpc-statd.service failed. mount[4907]: Job for rpc-statd.service failed. See "systemctl status rpc-statd.service" and "journalctl -xe" for details. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Tuesday, 24 February 2015, 07:43 GMT
Reason for closing: Works for me
Additional comments about closing: with rpcbind and nfs-server on the server side and rpcbind + nfs-client on the clients mounting v4 and v3 works well with current core packages.
Tuesday, 24 February 2015, 07:43 GMT
Reason for closing: Works for me
Additional comments about closing: with rpcbind and nfs-server on the server side and rpcbind + nfs-client on the clients mounting v4 and v3 works well with current core packages.
My NSF resources are not mounted (through fstab also).
NFS3 needs rpcbind.
I think the usual *hehe* problem with rpc.statd show always up, if a mere client tries to access an old NFSv3-Server. In this case, rpcbind.service is currently not mentioned for the client on the Wiki (should I add it?):
It seems to work for me with:
systemctl start nfs-client.target
systemctl start rpcbind.service
systemctl start rpc-statd.service
mount -t nfs [path_to_server] [mountpoint]
since 8 February 2015 nfs-idmapd fails and doesnt say why in the journal
systemd[1]: Failed to start NFSv4 ID-name mapping serv
-- Subject: Unit nfs-idmapd.service has failed
sudo journalctl _SYSTEMD_UNIT=rpc-statd.service
-- Reboot --
Feb 10 16:35:17 mars rpc.statd[561]: Version 1.3.2 starting
Feb 10 16:35:17 mars rpc.statd[561]: Flags: TI-RPC
Feb 10 16:35:17 mars rpc.statd[561]: Failed to read /var/lib/nfs/state: Success
Feb 10 16:35:17 mars rpc.statd[561]: Initializing NSM state
Feb 10 16:35:17 mars rpc.statd[561]: Running as root. chown /var/lib/nfs to choose different user
Feb 10 16:35:17 mars rpc.statd[561]: failed to create RPC listeners, exiting
sudo journalctl _SYSTEMD_UNIT=nfs-server.service
-- Reboot --
Feb 10 16:35:17 mars rpc.nfsd[571]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
Feb 10 16:35:17 mars rpc.nfsd[571]: rpc.nfsd: unable to set any sockets for nfsd
rpcbind to 0.2.1-5
nfs-utils to 1.3.1-1
Not sure if all of these are required at this point. I need to do family stuff now. Perhaps someone else can investigate with the rpcbind downgrade only and see if behavior is fixed. If not, try both rpcbind and nfs-utils.
EDIT: Forgot to mention that clients required a downgrade of libnfs to 1.9.6-1 to work with the downgraded server versions.
On Arch I run a Kerberized NFS client only, not an NFS server.
Also, libnfs needs to be downgraded to 1.9.6-1 for clients or else they are unable to connect when the server is using the downgraded rpcbind.
EDIT: I just read through
FS#41433and after seeing that one needs to implicitly start rpcbind now, everything seems to work: enable rpcbind and nfs-utils (which the wiki states) on the server. Reboot to verify....but I still need to use libnfs-1.9.6-1 so I opened
FS#43776I'm running rpcbind 0.2.2-2 and downgraded nfs-utils 1.3.1-1, and everything works like before.
I don't have libnfs installed.
nfs-utils (1.3.1-1) & rpcbind (0.2.1-5): works
nfs-utils (1.3.2-3) & rpcbind (0.2.2-2): BROKEN
Linux myhost 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64 GNU/Linux
which cannot launch if you don't enable rpcbind.
NFS3 needs rpcbind, NFS4 does not need rpcbind.