Description of problem: Server is RHEL 6, client is Fedora 19. I've wasted an hour attempting to mount a directory, but each variant gives me: mount.nfs: access denied by server while mounting onuma:/mnt/exports/trim-home/rjones/d Even mount -v is barely any more useful: mount.nfs4: timeout set for Thu Aug 1 16:29:43 2013 mount.nfs4: trying text-based options 'hard,intr,addr=fd00:dead:beef:feed:dad3:85ff:feaf:80b9,clientaddr=fd00:dead:beef:feed:201:c0ff:fe0c:432b' mount.nfs4: mount(2): Permission denied mount.nfs4: trying text-based options 'hard,intr,addr=192.168.0.249,clientaddr=192.168.0.170' mount.nfs4: mount(2): Permission denied mount.nfs4: access denied by server while mounting onuma:/mnt/exports/trim-home/rjones/d There is *no* other information anywhere about what permission is wrong or why it's wrong or what I can do to correct it. Nothing in /var/log/messages, /var/log/secure, dmesg. Nothing on the client or the server. Please note: This bug is not about a permissions problem. It's about making NFS errors useful and actionable. Version-Release number of selected component (if applicable): Client: nfs-utils-1.2.8-2.0.fc19.armv7hl Server: nfs-utils-1.2.3-36.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Try to mount something when you don't have permissions. 2. Look for the real error. Actual results: Real error is MIA. Expected results: The mount command (ideally) or at least /var/log/messages should contain detailed errors about what steps were being taken, what failed, and what the user can do to correct the error.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.