Description of problem: My desktop is an NFS client, with my home directory on a server. Hardware failures forced a reinstall of both server and client, and now my desktop machine is painfully slow. The log file shows that the client is getting the following error once every 5 seconds: Dec 9 23:06:58 leto kernel: [714958.020911] NFS: state manager: check lease failed on NFSv4 server filehost with error 93 This is accompanied by two error lines on the server: Dec 9 23:06:58 riva kernel: svc: 192.168.8.4, port=813: unknown version (4 for prog 100003, nfsd) Dec 9 23:06:58 riva kernel: svc: 192.168.8.4, port=813: unknown version (4 for prog 100003, nfsd) Error 93 appears to be "version not supported". This is correct. I have explicitly configured the server not to support v3 or v4 (because doing so caused slowdowns sufficiently bad as to render clients unusable). What I don't understand is why the client is requesting anything using v4. I've explicitly told it to use v2: leto:~# fgrep nfs /etc/fstab filehost:/audio /audio nfs nfsvers=2 0 0 filehost:/local /local nfs nfsvers=2 0 0 filehost:/local/home /local/home nfs nfsvers=2 0 0 filehost:/var/spool/mail /var/spool/mail nfs nfsvers=2 0 0 Version-Release number of selected component (if applicable): leto:~# rpm -q nfs-utils kernel nfs-utils-1.2.6-6.fc17.x86_64 kernel-3.3.4-5.fc17.x86_64 kernel-3.6.7-4.fc17.x86_64 kernel-3.6.8-2.fc17.x86_64 leto:~# uname -r 3.6.8-2.fc17.x86_64 How reproducible: Every time Steps to Reproduce: 1. Boot machine 2. Observe slowness 3. See errors in log files Actual results: Expected results: Additional info: On the server: riva:~# uname -r 2.6.32-279.14.1.el6.x86_64 riva:~# grep '^[^#]' /etc/sysconfig/nfs MOUNTD_NFS_V3="no" RPCNFSDARGS="-N 4"
Just a comment - you really should look at why you see bad performance in V3 and V4. V2 support is *ancient* and not actively worked on (even though it is unlikely to go away suddenly).
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.