Hide Forgot
Description of problem: When the NFS server is configured to only support NFSv4 (v3 disabled), a Fedora client that tries to mount a filesystem that does not exist, will keep trying various v3 entries before giving up after a long timeout. It should immediately return the "not found" error and stop instead of retrying with v3. Version-Release number of selected component (if applicable): nfs-utils-1.3.4-1.rc3.fc24.x86_64 How reproducible: always, but the client seems to cache the server response for a while and the delay only occurs on the first attempt. Steps to Reproduce: 1. Configure NFS server to only support NFSv4 (v3 disabled). File server in our case is a RHEL6 machine 2. Access a directory that does not exist on the server. We use automount to mount home directories. Mounting /home/.hidden (where .hidden does not exist on the server) triggers this. Since nautilus seems to search for .hidden frequently, this causes very long delays. 3. Actual results: Mount command takes way too long. Expected results: Mount command returns immediately with "not found" message. Additional info: Running the mount command manually to reproduce the problem shows that after receiving the not found error, mount.nfs4 retries with v3 options. If the fstype is set to nfs4, it should not try v3. Why is it retrying when the server returns No such file or directory?? [root@malachite ~]# mount -v -t nfs4 -o nodev,nosuid,intr bocq:/san/dept/system/_hidden /mnt mount.nfs4: timeout set for Tue Dec 6 20:24:39 2016 mount.nfs4: trying text-based options 'intr,vers=4.2,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): Protocol not supported mount.nfs4: trying text-based options 'intr,vers=4.1,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): Protocol not supported mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.33.138.169,clientaddr=10.33.133.204' mount.nfs4: mount(2): No such file or directory mount.nfs4: trying text-based options 'intr,addr=10.33.138.169' mount.nfs4: prog 100003, trying vers=3, prot=6 mount.nfs4: trying 10.33.138.169 prog 100003 vers 3 prot TCP port 2049 mount.nfs4: portmap query retrying: RPC: Program/version mismatch mount.nfs4: prog 100003, trying vers=3, prot=17 mount.nfs4: portmap query failed: RPC: Program not registered mount.nfs4: Connection timed out
This is a known regression that will be fixed by an upcoming update.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.