Remount as read only is showing busy , how to remount as read only safely?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite
1












When trying remount , mount /path busy always.



mount -o remount,ro /path
mount: /path is busy



Is there any method to remount it as read only safely ?
What is the method to check why it is busy ?
Have tried lsof but shows nothing .







share|improve this question























    up vote
    1
    down vote

    favorite
    1












    When trying remount , mount /path busy always.



    mount -o remount,ro /path
    mount: /path is busy



    Is there any method to remount it as read only safely ?
    What is the method to check why it is busy ?
    Have tried lsof but shows nothing .







    share|improve this question





















      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      When trying remount , mount /path busy always.



      mount -o remount,ro /path
      mount: /path is busy



      Is there any method to remount it as read only safely ?
      What is the method to check why it is busy ?
      Have tried lsof but shows nothing .







      share|improve this question











      When trying remount , mount /path busy always.



      mount -o remount,ro /path
      mount: /path is busy



      Is there any method to remount it as read only safely ?
      What is the method to check why it is busy ?
      Have tried lsof but shows nothing .









      share|improve this question










      share|improve this question




      share|improve this question









      asked Jun 7 at 10:53









      Amruth A

      787




      787




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          There isn't really a way to 'safely' force it read-only. Anything that did would either:



          1. Not really be read-only, because there would still be a file opened for write or append on the filesystem

          or:



          1. Crash whatever application has a writable file open on that mount point.

          As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.






          share|improve this answer





















            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',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );








             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f448393%2fremount-as-read-only-is-showing-busy-how-to-remount-as-read-only-safely%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote



            accepted










            There isn't really a way to 'safely' force it read-only. Anything that did would either:



            1. Not really be read-only, because there would still be a file opened for write or append on the filesystem

            or:



            1. Crash whatever application has a writable file open on that mount point.

            As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.






            share|improve this answer

























              up vote
              1
              down vote



              accepted










              There isn't really a way to 'safely' force it read-only. Anything that did would either:



              1. Not really be read-only, because there would still be a file opened for write or append on the filesystem

              or:



              1. Crash whatever application has a writable file open on that mount point.

              As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.






              share|improve this answer























                up vote
                1
                down vote



                accepted







                up vote
                1
                down vote



                accepted






                There isn't really a way to 'safely' force it read-only. Anything that did would either:



                1. Not really be read-only, because there would still be a file opened for write or append on the filesystem

                or:



                1. Crash whatever application has a writable file open on that mount point.

                As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.






                share|improve this answer













                There isn't really a way to 'safely' force it read-only. Anything that did would either:



                1. Not really be read-only, because there would still be a file opened for write or append on the filesystem

                or:



                1. Crash whatever application has a writable file open on that mount point.

                As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.







                share|improve this answer













                share|improve this answer



                share|improve this answer











                answered Jun 7 at 18:56









                Austin Hemmelgarn

                5,049915




                5,049915






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f448393%2fremount-as-read-only-is-showing-busy-how-to-remount-as-read-only-safely%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?