FS#42491 - [nfs-utils] [boot] rpc-statd won't start for user NFS mounts

Attached to Project: Arch Linux
Opened by Christopher Smith (chrylis) - Wednesday, 22 October 2014, 03:12 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 25 February 2015, 20:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have NFS mounts in my /etc/fstab that are listed as "user,noauto", and I have nfs-client active in systemd. When I try to mount a share as a user, I get the error message

Failed to start rpc-statd.service: Access denied
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

Manually starting rpc-statd as root, or mounting (and even then unmounting) any NFS share as root gets rpc-statd running, and I can then mount as a user.

I tried to enable rpc-statd, but I am told that "The unit files have no [Install] section."

Either rpc-statd should be automatically started with nfs-client (which seems to make the most sense), or it should be implicitly started when an NFS mount is attempted.

Steps to reproduce:

- Create an fstab with only "user,noauto" NFS shares.
- Attempt to mount an NFS share as a user.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 25 February 2015, 20:02 GMT
Reason for closing:  Not a bug
Additional comments about closing:  rpcbind needs to be enabled by the sysadmin nowadays. see our nfs wiki page.
Comment by Tobias Powalowski (tpowa) - Thursday, 05 February 2015, 13:44 GMT
I can confirm this issue, posted here:
http://article.gmane.org/gmane.linux.nfs/69167
NFS4 is not affected, perhaps you should try to use NFS4 instead of NFS3.
Comment by Tobias Powalowski (tpowa) - Thursday, 05 February 2015, 17:21 GMT
You could also add x-systemd.automount to mount options in /etc/fstab.
This way it's automounted when you access the destination.
Comment by Andreas Radke (AndyRTR) - Tuesday, 24 February 2015, 07:52 GMT
I guess rpcbind.service is not running or the changes required for rpcbind-less connections with v4 are not applied (https://bbs.archlinux.org/viewtopic.php?id=193629).

This one should be a user setup issue.

Loading...