nfsd: last server has exited, flushing export cache












0














Brief Summary on the issue:



NFS share on a CentOS6.9 system properly mounts and displays the directory when mounted on a Windows or Linux system but has trouble displaying the directory when mounted on Mac OS systems. After mounting the NFS share on a Mac OS system, Finder pinwheels as it attempts to load the contents of the directory.



Error message from /var/log/messages:



kernel: nfsd: last server has exited, flushing export cache
kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de)
kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory


Output of cat /etc/passwd | grep rpc



rpc:x:32:32:Rpcbind Daemon:/var/lib/rpcbind:/sbin/nologin
rpcuser:x:29:29:RPC Service User:/var/lib/nfs:/sbin/nologin


I'm having a really hard time understanding the error message in /var/log/messages, what is wrong with nfs? I found a few other posts online that pointed to the path in /etc/passwd being incorrect, even though others in that post stated it should be fine.



I double checked the path listed in /etc/passwd and found there is no such rpcbind folder in /var/lib, but there is one in /var/cache which the person in that post stated is the correct path. Is that path possibly causing the issue?



The next steps I plan on taking is restarting nfs and rpcbind services and if that fails, then reinstalling with yum reinstall nfs-util rpcbind. If both of these methods fail then I'll consider changing the path from /var/lib to /var/cache.



Has anyone ever come across this issue before?



Bug Zilla Post



centos.org forum post










share|improve this question



























    0














    Brief Summary on the issue:



    NFS share on a CentOS6.9 system properly mounts and displays the directory when mounted on a Windows or Linux system but has trouble displaying the directory when mounted on Mac OS systems. After mounting the NFS share on a Mac OS system, Finder pinwheels as it attempts to load the contents of the directory.



    Error message from /var/log/messages:



    kernel: nfsd: last server has exited, flushing export cache
    kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de)
    kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory


    Output of cat /etc/passwd | grep rpc



    rpc:x:32:32:Rpcbind Daemon:/var/lib/rpcbind:/sbin/nologin
    rpcuser:x:29:29:RPC Service User:/var/lib/nfs:/sbin/nologin


    I'm having a really hard time understanding the error message in /var/log/messages, what is wrong with nfs? I found a few other posts online that pointed to the path in /etc/passwd being incorrect, even though others in that post stated it should be fine.



    I double checked the path listed in /etc/passwd and found there is no such rpcbind folder in /var/lib, but there is one in /var/cache which the person in that post stated is the correct path. Is that path possibly causing the issue?



    The next steps I plan on taking is restarting nfs and rpcbind services and if that fails, then reinstalling with yum reinstall nfs-util rpcbind. If both of these methods fail then I'll consider changing the path from /var/lib to /var/cache.



    Has anyone ever come across this issue before?



    Bug Zilla Post



    centos.org forum post










    share|improve this question

























      0












      0








      0







      Brief Summary on the issue:



      NFS share on a CentOS6.9 system properly mounts and displays the directory when mounted on a Windows or Linux system but has trouble displaying the directory when mounted on Mac OS systems. After mounting the NFS share on a Mac OS system, Finder pinwheels as it attempts to load the contents of the directory.



      Error message from /var/log/messages:



      kernel: nfsd: last server has exited, flushing export cache
      kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de)
      kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory


      Output of cat /etc/passwd | grep rpc



      rpc:x:32:32:Rpcbind Daemon:/var/lib/rpcbind:/sbin/nologin
      rpcuser:x:29:29:RPC Service User:/var/lib/nfs:/sbin/nologin


      I'm having a really hard time understanding the error message in /var/log/messages, what is wrong with nfs? I found a few other posts online that pointed to the path in /etc/passwd being incorrect, even though others in that post stated it should be fine.



      I double checked the path listed in /etc/passwd and found there is no such rpcbind folder in /var/lib, but there is one in /var/cache which the person in that post stated is the correct path. Is that path possibly causing the issue?



      The next steps I plan on taking is restarting nfs and rpcbind services and if that fails, then reinstalling with yum reinstall nfs-util rpcbind. If both of these methods fail then I'll consider changing the path from /var/lib to /var/cache.



      Has anyone ever come across this issue before?



      Bug Zilla Post



      centos.org forum post










      share|improve this question













      Brief Summary on the issue:



      NFS share on a CentOS6.9 system properly mounts and displays the directory when mounted on a Windows or Linux system but has trouble displaying the directory when mounted on Mac OS systems. After mounting the NFS share on a Mac OS system, Finder pinwheels as it attempts to load the contents of the directory.



      Error message from /var/log/messages:



      kernel: nfsd: last server has exited, flushing export cache
      kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de)
      kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory


      Output of cat /etc/passwd | grep rpc



      rpc:x:32:32:Rpcbind Daemon:/var/lib/rpcbind:/sbin/nologin
      rpcuser:x:29:29:RPC Service User:/var/lib/nfs:/sbin/nologin


      I'm having a really hard time understanding the error message in /var/log/messages, what is wrong with nfs? I found a few other posts online that pointed to the path in /etc/passwd being incorrect, even though others in that post stated it should be fine.



      I double checked the path listed in /etc/passwd and found there is no such rpcbind folder in /var/lib, but there is one in /var/cache which the person in that post stated is the correct path. Is that path possibly causing the issue?



      The next steps I plan on taking is restarting nfs and rpcbind services and if that fails, then reinstalling with yum reinstall nfs-util rpcbind. If both of these methods fail then I'll consider changing the path from /var/lib to /var/cache.



      Has anyone ever come across this issue before?



      Bug Zilla Post



      centos.org forum post







      linux unix centos nfs






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 6 at 23:02









      Aren Tahmasian

      14




      14






















          1 Answer
          1






          active

          oldest

          votes


















          0














          If my understanding is correct, the issue itself is not with NFS but rather Finder. Windows and Linux clients did not display performance issues when connecting to the NFS mounts.



          These are the steps I took to resolve the performance issue on Finder:




          1. Stopped rpcbind service

          2. Stopped nfslock service

          3. Executed command rm -rf /var/lib/nfs/statd/sm/*

          4. Executed command rm -rf /var/lib/nfs/statd/sm.bak/*

          5. Started rpcbind service

          6. Started nfslock service

          7. Restarted nfs service


          Afterwards Finder was able to open and list directories with ease. I'm not exactly sure why this worked but the effect was significant.



          Lastly, I did try to add symlinks at /var/lib/rpcbind to /var/cache/rpcbind but this made no difference (of course I restarted all the appropriate services) so I defaulted back to the original setup.



          EDIT: The main culprit was hidden files, millions of them. Finder had a terrible time handling all these files. Removing them fixed the performance better than anything else I've tried.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1311598%2fnfsd-last-server-has-exited-flushing-export-cache%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            If my understanding is correct, the issue itself is not with NFS but rather Finder. Windows and Linux clients did not display performance issues when connecting to the NFS mounts.



            These are the steps I took to resolve the performance issue on Finder:




            1. Stopped rpcbind service

            2. Stopped nfslock service

            3. Executed command rm -rf /var/lib/nfs/statd/sm/*

            4. Executed command rm -rf /var/lib/nfs/statd/sm.bak/*

            5. Started rpcbind service

            6. Started nfslock service

            7. Restarted nfs service


            Afterwards Finder was able to open and list directories with ease. I'm not exactly sure why this worked but the effect was significant.



            Lastly, I did try to add symlinks at /var/lib/rpcbind to /var/cache/rpcbind but this made no difference (of course I restarted all the appropriate services) so I defaulted back to the original setup.



            EDIT: The main culprit was hidden files, millions of them. Finder had a terrible time handling all these files. Removing them fixed the performance better than anything else I've tried.






            share|improve this answer




























              0














              If my understanding is correct, the issue itself is not with NFS but rather Finder. Windows and Linux clients did not display performance issues when connecting to the NFS mounts.



              These are the steps I took to resolve the performance issue on Finder:




              1. Stopped rpcbind service

              2. Stopped nfslock service

              3. Executed command rm -rf /var/lib/nfs/statd/sm/*

              4. Executed command rm -rf /var/lib/nfs/statd/sm.bak/*

              5. Started rpcbind service

              6. Started nfslock service

              7. Restarted nfs service


              Afterwards Finder was able to open and list directories with ease. I'm not exactly sure why this worked but the effect was significant.



              Lastly, I did try to add symlinks at /var/lib/rpcbind to /var/cache/rpcbind but this made no difference (of course I restarted all the appropriate services) so I defaulted back to the original setup.



              EDIT: The main culprit was hidden files, millions of them. Finder had a terrible time handling all these files. Removing them fixed the performance better than anything else I've tried.






              share|improve this answer


























                0












                0








                0






                If my understanding is correct, the issue itself is not with NFS but rather Finder. Windows and Linux clients did not display performance issues when connecting to the NFS mounts.



                These are the steps I took to resolve the performance issue on Finder:




                1. Stopped rpcbind service

                2. Stopped nfslock service

                3. Executed command rm -rf /var/lib/nfs/statd/sm/*

                4. Executed command rm -rf /var/lib/nfs/statd/sm.bak/*

                5. Started rpcbind service

                6. Started nfslock service

                7. Restarted nfs service


                Afterwards Finder was able to open and list directories with ease. I'm not exactly sure why this worked but the effect was significant.



                Lastly, I did try to add symlinks at /var/lib/rpcbind to /var/cache/rpcbind but this made no difference (of course I restarted all the appropriate services) so I defaulted back to the original setup.



                EDIT: The main culprit was hidden files, millions of them. Finder had a terrible time handling all these files. Removing them fixed the performance better than anything else I've tried.






                share|improve this answer














                If my understanding is correct, the issue itself is not with NFS but rather Finder. Windows and Linux clients did not display performance issues when connecting to the NFS mounts.



                These are the steps I took to resolve the performance issue on Finder:




                1. Stopped rpcbind service

                2. Stopped nfslock service

                3. Executed command rm -rf /var/lib/nfs/statd/sm/*

                4. Executed command rm -rf /var/lib/nfs/statd/sm.bak/*

                5. Started rpcbind service

                6. Started nfslock service

                7. Restarted nfs service


                Afterwards Finder was able to open and list directories with ease. I'm not exactly sure why this worked but the effect was significant.



                Lastly, I did try to add symlinks at /var/lib/rpcbind to /var/cache/rpcbind but this made no difference (of course I restarted all the appropriate services) so I defaulted back to the original setup.



                EDIT: The main culprit was hidden files, millions of them. Finder had a terrible time handling all these files. Removing them fixed the performance better than anything else I've tried.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 11 at 22:47

























                answered Apr 19 at 17:25









                Aren Tahmasian

                14




                14






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1311598%2fnfsd-last-server-has-exited-flushing-export-cache%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

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕