FS#17721 - [nfs-utils] mount.nfs: Operation not permitted
Attached to Project:
Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Wednesday, 06 January 2010, 10:37 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 January 2011, 20:11 GMT
Opened by Andreas Baumann (andreas_baumann) - Wednesday, 06 January 2010, 10:37 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 January 2011, 20:11 GMT
|
Details
Description:
Mounts stopped working with the newest update (nfs-utils 1.2.1-2) with: mount.nfs: Operation not permitted The same mounts worked without any trouble before. They also work if using for instance a Centos 5.4 against the same NFS server. No configuration on server or client side has been changed. No funny firewalls or /etc/hosts.* settings. Additional errors in the logfile (/var/log/messages): rpc.statd: Unable to read state from '/var/lib/nfs/state': errno 0 (Success) sm-notify: Already notifying clients; Exiting! Steps to reproduce: |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 26 January 2011, 20:11 GMT
Reason for closing: Fixed
Additional comments about closing: seems to be fixed according to comments
Wednesday, 26 January 2011, 20:11 GMT
Reason for closing: Fixed
Additional comments about closing: seems to be fixed according to comments
update the /etc/idmapd.conf or reads the NFS4 section in the Arch Wiki and suddenly mount
happens with nfs4 per default.. :-)
I personally don't think, that NFS 4 is stable enough (too many quircks around ACLs,
cooperation with Samba 4, etc.)
a) configure rpc.idmap properly and use NFS4 (client and server)
b) use mount option 'vers=3' and continue to use NFS3 without
changes to the server or other changes to the client but to
set the vers=3 option
mount.nfs share mount_point -o 'vers=3'
or in /etc/fstab in a line like:
share mount_point nfs vers=3 0 0
and I completly reinstalled archlinux with nfs-utils 1.2.2-3,
I didn't have any problems anymore.