Why would NFS have lag unless continuously accessed?












0














I am running a version 4 NFS server on a Salix server with kernel 3.10.17. I am mounting the NFS share with the command "sudo mount -t nfs 10.0.0.150:/share /mountpoint" on my client machine, which is the most recent version of Xubuntu (but I've had this problem with this NFS share across several different flavors and versions of Ubuntu clients over the past several years). The first time I access this mount point, such as through the file manager (just for an example, but any other kind of access has the same symptom), I have to wait 20 seconds before the data from the share loads. Once that happens, I can browse through the shared folders without any delay, at least until I let the mount go dormant (meaning I don't try to access anything under it) for about a minute, after which I would experience the delay again. My client is also NFS v4.



Here is the output of nfsstat -m on the client:
rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.0.214,local_lock=none,addr=10.0.0.150



I'm not sure if this is relevant, but I am sharing the same folder on the server through SAMBA for my Windows clients, and there are no issues with the SAMBA share.










share|improve this question







New contributor




Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0














    I am running a version 4 NFS server on a Salix server with kernel 3.10.17. I am mounting the NFS share with the command "sudo mount -t nfs 10.0.0.150:/share /mountpoint" on my client machine, which is the most recent version of Xubuntu (but I've had this problem with this NFS share across several different flavors and versions of Ubuntu clients over the past several years). The first time I access this mount point, such as through the file manager (just for an example, but any other kind of access has the same symptom), I have to wait 20 seconds before the data from the share loads. Once that happens, I can browse through the shared folders without any delay, at least until I let the mount go dormant (meaning I don't try to access anything under it) for about a minute, after which I would experience the delay again. My client is also NFS v4.



    Here is the output of nfsstat -m on the client:
    rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.0.214,local_lock=none,addr=10.0.0.150



    I'm not sure if this is relevant, but I am sharing the same folder on the server through SAMBA for my Windows clients, and there are no issues with the SAMBA share.










    share|improve this question







    New contributor




    Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0







      I am running a version 4 NFS server on a Salix server with kernel 3.10.17. I am mounting the NFS share with the command "sudo mount -t nfs 10.0.0.150:/share /mountpoint" on my client machine, which is the most recent version of Xubuntu (but I've had this problem with this NFS share across several different flavors and versions of Ubuntu clients over the past several years). The first time I access this mount point, such as through the file manager (just for an example, but any other kind of access has the same symptom), I have to wait 20 seconds before the data from the share loads. Once that happens, I can browse through the shared folders without any delay, at least until I let the mount go dormant (meaning I don't try to access anything under it) for about a minute, after which I would experience the delay again. My client is also NFS v4.



      Here is the output of nfsstat -m on the client:
      rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.0.214,local_lock=none,addr=10.0.0.150



      I'm not sure if this is relevant, but I am sharing the same folder on the server through SAMBA for my Windows clients, and there are no issues with the SAMBA share.










      share|improve this question







      New contributor




      Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I am running a version 4 NFS server on a Salix server with kernel 3.10.17. I am mounting the NFS share with the command "sudo mount -t nfs 10.0.0.150:/share /mountpoint" on my client machine, which is the most recent version of Xubuntu (but I've had this problem with this NFS share across several different flavors and versions of Ubuntu clients over the past several years). The first time I access this mount point, such as through the file manager (just for an example, but any other kind of access has the same symptom), I have to wait 20 seconds before the data from the share loads. Once that happens, I can browse through the shared folders without any delay, at least until I let the mount go dormant (meaning I don't try to access anything under it) for about a minute, after which I would experience the delay again. My client is also NFS v4.



      Here is the output of nfsstat -m on the client:
      rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.0.214,local_lock=none,addr=10.0.0.150



      I'm not sure if this is relevant, but I am sharing the same folder on the server through SAMBA for my Windows clients, and there are no issues with the SAMBA share.







      nfs






      share|improve this question







      New contributor




      Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 11 mins ago









      Sean Dalton

      1




      1




      New contributor




      Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Sean Dalton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Sean Dalton is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492374%2fwhy-would-nfs-have-lag-unless-continuously-accessed%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Sean Dalton is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Sean Dalton is a new contributor. Be nice, and check out our Code of Conduct.













          Sean Dalton is a new contributor. Be nice, and check out our Code of Conduct.












          Sean Dalton is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492374%2fwhy-would-nfs-have-lag-unless-continuously-accessed%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt