btrfs ERROR: error during balancing - No space left on device

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











up vote
13
down vote

favorite
4












My Kubuntu 12.04 system ran out of space on on the root partition and will not boot. The command df -h shows a lot of space available (with only 37% used):



/dev/sda2 45G 17G 29G 37%


The following page indicates that I should run the balance command:



https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_on_device.22_errors.2C_but_df_says_I.27ve_got_lots_of_space



$ sudo btrfs fi balance start -dusage=5 /mount/point


I'm not entirely confident that this is the best approach, but it is the only one I found. However, when I run that command, I get this error:



ERROR: error during balancing '/blah/blah/blah' - No space left on device


I get the same error with:



$ sudo btrfs fi balance start -dusage=1 /mount/point


What is the right solution?










share|improve this question

























    up vote
    13
    down vote

    favorite
    4












    My Kubuntu 12.04 system ran out of space on on the root partition and will not boot. The command df -h shows a lot of space available (with only 37% used):



    /dev/sda2 45G 17G 29G 37%


    The following page indicates that I should run the balance command:



    https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_on_device.22_errors.2C_but_df_says_I.27ve_got_lots_of_space



    $ sudo btrfs fi balance start -dusage=5 /mount/point


    I'm not entirely confident that this is the best approach, but it is the only one I found. However, when I run that command, I get this error:



    ERROR: error during balancing '/blah/blah/blah' - No space left on device


    I get the same error with:



    $ sudo btrfs fi balance start -dusage=1 /mount/point


    What is the right solution?










    share|improve this question























      up vote
      13
      down vote

      favorite
      4









      up vote
      13
      down vote

      favorite
      4






      4





      My Kubuntu 12.04 system ran out of space on on the root partition and will not boot. The command df -h shows a lot of space available (with only 37% used):



      /dev/sda2 45G 17G 29G 37%


      The following page indicates that I should run the balance command:



      https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_on_device.22_errors.2C_but_df_says_I.27ve_got_lots_of_space



      $ sudo btrfs fi balance start -dusage=5 /mount/point


      I'm not entirely confident that this is the best approach, but it is the only one I found. However, when I run that command, I get this error:



      ERROR: error during balancing '/blah/blah/blah' - No space left on device


      I get the same error with:



      $ sudo btrfs fi balance start -dusage=1 /mount/point


      What is the right solution?










      share|improve this question













      My Kubuntu 12.04 system ran out of space on on the root partition and will not boot. The command df -h shows a lot of space available (with only 37% used):



      /dev/sda2 45G 17G 29G 37%


      The following page indicates that I should run the balance command:



      https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_on_device.22_errors.2C_but_df_says_I.27ve_got_lots_of_space



      $ sudo btrfs fi balance start -dusage=5 /mount/point


      I'm not entirely confident that this is the best approach, but it is the only one I found. However, when I run that command, I get this error:



      ERROR: error during balancing '/blah/blah/blah' - No space left on device


      I get the same error with:



      $ sudo btrfs fi balance start -dusage=1 /mount/point


      What is the right solution?







      filesystems btrfs






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 16 '14 at 4:30









      MountainX

      4,6202368118




      4,6202368118




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          13
          down vote



          accepted










          There are ways to get balance to run in this situation.



          sudo btrfs fi show
          sudo btrfs fi df /mount/point
          sudo btrfs fi balance start -dusage=10 /mount/point


          If the balance command ends with "Done, had to relocate 0 out of XX chunks", then you need to increase the "dusage" percentage parameter till at least one chunk is relocated.



          if the balance command fails with:



          ERROR: error during balancing '/blah/blah/blah' - No space left on device


          You might actually need to delete files from the device to make some room. Then run the balance command again.



          However, thanks to Marc's Blog: btrfs - Fixing Btrfs Filesystem Full Problems here is another option:




          One trick to get around this is to add a device (even a USB key will
          do) to your btrfs filesystem. This should allow balance to start, and
          then you can remove the device with btrfs device delete when the
          balance is finished. It's also been said on the list that kernel 3.14
          can fix some balancing issues that older kernels can't, so give that a
          shot if your kernel is old.







          share|improve this answer


















          • 5




            I've found that occasionally I've also needed to mount -oremount,clear_cache /mountpoint as well to fix the free space calculations. (They become corrupted...)
            – rrauenza
            Jun 20 '16 at 23:30







          • 1




            @rrauenza, thanks! You should add that as an answer :)
            – mwfearnley
            Apr 3 at 11:20

















          up vote
          0
          down vote













          I tried everything in the accepted answer, and Marc's blog, including incrementing the -dusage parameter and adding another block device, all to no avail. Even after deleting some files and freeing up a little space on the disk which was full, balance was not able to complete. For some reason it always seemed to be moving data onto the nearly full disk. In the end what did work for me was restricting balancing to the full device:



          btrfs balance start -ddevid=<dev_id> <path>


          where the dev_id can be found with:



          btrfs fi show 





          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%2f174446%2fbtrfs-error-error-during-balancing-no-space-left-on-device%23new-answer', 'question_page');

            );

            Post as a guest






























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            13
            down vote



            accepted










            There are ways to get balance to run in this situation.



            sudo btrfs fi show
            sudo btrfs fi df /mount/point
            sudo btrfs fi balance start -dusage=10 /mount/point


            If the balance command ends with "Done, had to relocate 0 out of XX chunks", then you need to increase the "dusage" percentage parameter till at least one chunk is relocated.



            if the balance command fails with:



            ERROR: error during balancing '/blah/blah/blah' - No space left on device


            You might actually need to delete files from the device to make some room. Then run the balance command again.



            However, thanks to Marc's Blog: btrfs - Fixing Btrfs Filesystem Full Problems here is another option:




            One trick to get around this is to add a device (even a USB key will
            do) to your btrfs filesystem. This should allow balance to start, and
            then you can remove the device with btrfs device delete when the
            balance is finished. It's also been said on the list that kernel 3.14
            can fix some balancing issues that older kernels can't, so give that a
            shot if your kernel is old.







            share|improve this answer


















            • 5




              I've found that occasionally I've also needed to mount -oremount,clear_cache /mountpoint as well to fix the free space calculations. (They become corrupted...)
              – rrauenza
              Jun 20 '16 at 23:30







            • 1




              @rrauenza, thanks! You should add that as an answer :)
              – mwfearnley
              Apr 3 at 11:20














            up vote
            13
            down vote



            accepted










            There are ways to get balance to run in this situation.



            sudo btrfs fi show
            sudo btrfs fi df /mount/point
            sudo btrfs fi balance start -dusage=10 /mount/point


            If the balance command ends with "Done, had to relocate 0 out of XX chunks", then you need to increase the "dusage" percentage parameter till at least one chunk is relocated.



            if the balance command fails with:



            ERROR: error during balancing '/blah/blah/blah' - No space left on device


            You might actually need to delete files from the device to make some room. Then run the balance command again.



            However, thanks to Marc's Blog: btrfs - Fixing Btrfs Filesystem Full Problems here is another option:




            One trick to get around this is to add a device (even a USB key will
            do) to your btrfs filesystem. This should allow balance to start, and
            then you can remove the device with btrfs device delete when the
            balance is finished. It's also been said on the list that kernel 3.14
            can fix some balancing issues that older kernels can't, so give that a
            shot if your kernel is old.







            share|improve this answer


















            • 5




              I've found that occasionally I've also needed to mount -oremount,clear_cache /mountpoint as well to fix the free space calculations. (They become corrupted...)
              – rrauenza
              Jun 20 '16 at 23:30







            • 1




              @rrauenza, thanks! You should add that as an answer :)
              – mwfearnley
              Apr 3 at 11:20












            up vote
            13
            down vote



            accepted







            up vote
            13
            down vote



            accepted






            There are ways to get balance to run in this situation.



            sudo btrfs fi show
            sudo btrfs fi df /mount/point
            sudo btrfs fi balance start -dusage=10 /mount/point


            If the balance command ends with "Done, had to relocate 0 out of XX chunks", then you need to increase the "dusage" percentage parameter till at least one chunk is relocated.



            if the balance command fails with:



            ERROR: error during balancing '/blah/blah/blah' - No space left on device


            You might actually need to delete files from the device to make some room. Then run the balance command again.



            However, thanks to Marc's Blog: btrfs - Fixing Btrfs Filesystem Full Problems here is another option:




            One trick to get around this is to add a device (even a USB key will
            do) to your btrfs filesystem. This should allow balance to start, and
            then you can remove the device with btrfs device delete when the
            balance is finished. It's also been said on the list that kernel 3.14
            can fix some balancing issues that older kernels can't, so give that a
            shot if your kernel is old.







            share|improve this answer














            There are ways to get balance to run in this situation.



            sudo btrfs fi show
            sudo btrfs fi df /mount/point
            sudo btrfs fi balance start -dusage=10 /mount/point


            If the balance command ends with "Done, had to relocate 0 out of XX chunks", then you need to increase the "dusage" percentage parameter till at least one chunk is relocated.



            if the balance command fails with:



            ERROR: error during balancing '/blah/blah/blah' - No space left on device


            You might actually need to delete files from the device to make some room. Then run the balance command again.



            However, thanks to Marc's Blog: btrfs - Fixing Btrfs Filesystem Full Problems here is another option:




            One trick to get around this is to add a device (even a USB key will
            do) to your btrfs filesystem. This should allow balance to start, and
            then you can remove the device with btrfs device delete when the
            balance is finished. It's also been said on the list that kernel 3.14
            can fix some balancing issues that older kernels can't, so give that a
            shot if your kernel is old.








            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 16 '14 at 7:15

























            answered Dec 16 '14 at 6:55









            MountainX

            4,6202368118




            4,6202368118







            • 5




              I've found that occasionally I've also needed to mount -oremount,clear_cache /mountpoint as well to fix the free space calculations. (They become corrupted...)
              – rrauenza
              Jun 20 '16 at 23:30







            • 1




              @rrauenza, thanks! You should add that as an answer :)
              – mwfearnley
              Apr 3 at 11:20












            • 5




              I've found that occasionally I've also needed to mount -oremount,clear_cache /mountpoint as well to fix the free space calculations. (They become corrupted...)
              – rrauenza
              Jun 20 '16 at 23:30







            • 1




              @rrauenza, thanks! You should add that as an answer :)
              – mwfearnley
              Apr 3 at 11:20







            5




            5




            I've found that occasionally I've also needed to mount -oremount,clear_cache /mountpoint as well to fix the free space calculations. (They become corrupted...)
            – rrauenza
            Jun 20 '16 at 23:30





            I've found that occasionally I've also needed to mount -oremount,clear_cache /mountpoint as well to fix the free space calculations. (They become corrupted...)
            – rrauenza
            Jun 20 '16 at 23:30





            1




            1




            @rrauenza, thanks! You should add that as an answer :)
            – mwfearnley
            Apr 3 at 11:20




            @rrauenza, thanks! You should add that as an answer :)
            – mwfearnley
            Apr 3 at 11:20












            up vote
            0
            down vote













            I tried everything in the accepted answer, and Marc's blog, including incrementing the -dusage parameter and adding another block device, all to no avail. Even after deleting some files and freeing up a little space on the disk which was full, balance was not able to complete. For some reason it always seemed to be moving data onto the nearly full disk. In the end what did work for me was restricting balancing to the full device:



            btrfs balance start -ddevid=<dev_id> <path>


            where the dev_id can be found with:



            btrfs fi show 





            share|improve this answer
























              up vote
              0
              down vote













              I tried everything in the accepted answer, and Marc's blog, including incrementing the -dusage parameter and adding another block device, all to no avail. Even after deleting some files and freeing up a little space on the disk which was full, balance was not able to complete. For some reason it always seemed to be moving data onto the nearly full disk. In the end what did work for me was restricting balancing to the full device:



              btrfs balance start -ddevid=<dev_id> <path>


              where the dev_id can be found with:



              btrfs fi show 





              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                I tried everything in the accepted answer, and Marc's blog, including incrementing the -dusage parameter and adding another block device, all to no avail. Even after deleting some files and freeing up a little space on the disk which was full, balance was not able to complete. For some reason it always seemed to be moving data onto the nearly full disk. In the end what did work for me was restricting balancing to the full device:



                btrfs balance start -ddevid=<dev_id> <path>


                where the dev_id can be found with:



                btrfs fi show 





                share|improve this answer












                I tried everything in the accepted answer, and Marc's blog, including incrementing the -dusage parameter and adding another block device, all to no avail. Even after deleting some files and freeing up a little space on the disk which was full, balance was not able to complete. For some reason it always seemed to be moving data onto the nearly full disk. In the end what did work for me was restricting balancing to the full device:



                btrfs balance start -ddevid=<dev_id> <path>


                where the dev_id can be found with:



                btrfs fi show 






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Aug 31 at 11:39









                z7sg

                1112




                1112



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f174446%2fbtrfs-error-error-during-balancing-no-space-left-on-device%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?