Cannot shrink btrfs filesystem although there is still data and metadata space left : ERROR: unable to resize...

Could a dragon use its wings to swim?

Computationally populating tables with probability data

Does higher Oxidation/ reduction potential translate to higher energy storage in battery?

Airplane gently rocking its wings during whole flight

What difference does it make using sed with/without whitespaces?

Where do students learn to solve polynomial equations these days?

how one can write a nice vector parser, something that does pgfvecparse{A=B-C; D=E x F;}

Do scriptures give a method to recognize a truly self-realized person/jivanmukta?

What was Carter Burke's job for "the company" in Aliens?

Is fine stranded wire ok for main supply line?

Strange use of "whether ... than ..." in official text

Help understanding this unsettling image of Titan, Epimetheus, and Saturn's rings?

Why am I getting "Static method cannot be referenced from a non static context: String String.valueOf(Object)"?

Why did early computer designers eschew integers?

free fall ellipse or parabola?

Is it correct to say moon starry nights?

Does Germany produce more waste than the US?

What would be the main consequences for a country leaving the WTO?

Is dried pee considered dirt?

Easy to read palindrome checker

How to Implement Deterministic Encryption Safely in .NET

vector calculus integration identity problem

Small nick on power cord from an electric alarm clock, and copper wiring exposed but intact

"Eavesdropping" vs "Listen in on"



Cannot shrink btrfs filesystem although there is still data and metadata space left : ERROR: unable to resize '/home': No space left on device



The Next CEO of Stack OverflowMount two btrfs subvolumes simultaneouslyrsnapshot frequently ext3-fs error: “ext3_lookup: deleted inode referenced:”btrfs write operations hang when appending to filesext4 mount flags for 10+ mill files storage“No space left on device” error despite having plenty of space, on btrfsIs it safe to continue working during btrfs balance operation?How to recover unrecoverable errors in a btrfs RAID1 volume?Does the ReFS filesystem reserve space for itself?Can we add more volumes/disks to an existing mounted ext3/ext4 mountpoint?BTRFS unmountable after cold reboot (total_rw_bytes is twice too big)












2















I cannot shrink btrfs filesystem although there is still data and metadata space left :





$ sudo btrfs filesystem resize -11G /home;echo $?
Resize '/home' of '-11G'
ERROR: unable to resize '/home': No space left on device
1


Here are some btrfs filesystem info about /home :



$ sudo btrfs filesystem df /home | column -t
Data, single: total=92.01GiB, used=80.68GiB
System, DUP: total=8.00MiB, used=16.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=1.00GiB, used=631.41MiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=224.00MiB, used=0.00B
$ sudo btrfs filesystem show /home
Label: none uuid: c7ee56a8-ef45-46c8-86d1-13879201a1e7
Total devices 1 FS bytes used 81.30GiB
devid 1 size 100.00GiB used 94.04GiB path /dev/mapper/home_VG-home

$ sudo btrfs filesystem usage -T /home
Overall:
Device size: 100.00GiB
Device allocated: 94.04GiB
Device unallocated: 5.96GiB
Device missing: 0.00B
Used: 81.91GiB
Free (estimated): 17.29GiB (min: 14.31GiB)
Data ratio: 1.00
Metadata ratio: 1.99
Global reserve: 224.00MiB (used: 0.00B)

Data Metadata Metadata System System
Id Path single single DUP single DUP Unallocated
-- --------- -------- -------- --------- ------- -------- -----------
1 /dev/dm-0 92.01GiB 8.00MiB 2.00GiB 4.00MiB 16.00MiB 5.96GiB
-- --------- -------- -------- --------- ------- -------- -----------
Total 92.01GiB 8.00MiB 1.00GiB 4.00MiB 8.00MiB 5.96GiB
Used 80.68GiB 0.00B 631.41MiB 0.00B 16.00KiB


and here the output of dmesg :



$ dmesg | tail -11
[44202.411949] BTRFS info (device dm-0): new size for /dev/dm-0 is 97706311680
[44202.412156] BTRFS info (device dm-0): relocating block group 120288444416 flags 1
[44208.119721] BTRFS info (device dm-0): relocating block group 119214702592 flags 1
[44211.611669] BTRFS info (device dm-0): relocating block group 118140960768 flags 1
[44212.495603] BTRFS info (device dm-0): relocating block group 117067218944 flags 1
[44213.006830] BTRFS info (device dm-0): relocating block group 95592382464 flags 1
[44216.613870] BTRFS info (device dm-0): relocating block group 120288444416 flags 1
[44222.780073] BTRFS info (device dm-0): relocating block group 119214702592 flags 1
[44225.843279] BTRFS info (device dm-0): relocating block group 118140960768 flags 1
[44226.575236] BTRFS info (device dm-0): relocating block group 117067218944 flags 1
[44226.930918] BTRFS info (device dm-0): relocating block group 95592382464 flags 1


Can you help me ?










share|improve this question





























    2















    I cannot shrink btrfs filesystem although there is still data and metadata space left :





    $ sudo btrfs filesystem resize -11G /home;echo $?
    Resize '/home' of '-11G'
    ERROR: unable to resize '/home': No space left on device
    1


    Here are some btrfs filesystem info about /home :



    $ sudo btrfs filesystem df /home | column -t
    Data, single: total=92.01GiB, used=80.68GiB
    System, DUP: total=8.00MiB, used=16.00KiB
    System, single: total=4.00MiB, used=0.00B
    Metadata, DUP: total=1.00GiB, used=631.41MiB
    Metadata, single: total=8.00MiB, used=0.00B
    GlobalReserve, single: total=224.00MiB, used=0.00B
    $ sudo btrfs filesystem show /home
    Label: none uuid: c7ee56a8-ef45-46c8-86d1-13879201a1e7
    Total devices 1 FS bytes used 81.30GiB
    devid 1 size 100.00GiB used 94.04GiB path /dev/mapper/home_VG-home

    $ sudo btrfs filesystem usage -T /home
    Overall:
    Device size: 100.00GiB
    Device allocated: 94.04GiB
    Device unallocated: 5.96GiB
    Device missing: 0.00B
    Used: 81.91GiB
    Free (estimated): 17.29GiB (min: 14.31GiB)
    Data ratio: 1.00
    Metadata ratio: 1.99
    Global reserve: 224.00MiB (used: 0.00B)

    Data Metadata Metadata System System
    Id Path single single DUP single DUP Unallocated
    -- --------- -------- -------- --------- ------- -------- -----------
    1 /dev/dm-0 92.01GiB 8.00MiB 2.00GiB 4.00MiB 16.00MiB 5.96GiB
    -- --------- -------- -------- --------- ------- -------- -----------
    Total 92.01GiB 8.00MiB 1.00GiB 4.00MiB 8.00MiB 5.96GiB
    Used 80.68GiB 0.00B 631.41MiB 0.00B 16.00KiB


    and here the output of dmesg :



    $ dmesg | tail -11
    [44202.411949] BTRFS info (device dm-0): new size for /dev/dm-0 is 97706311680
    [44202.412156] BTRFS info (device dm-0): relocating block group 120288444416 flags 1
    [44208.119721] BTRFS info (device dm-0): relocating block group 119214702592 flags 1
    [44211.611669] BTRFS info (device dm-0): relocating block group 118140960768 flags 1
    [44212.495603] BTRFS info (device dm-0): relocating block group 117067218944 flags 1
    [44213.006830] BTRFS info (device dm-0): relocating block group 95592382464 flags 1
    [44216.613870] BTRFS info (device dm-0): relocating block group 120288444416 flags 1
    [44222.780073] BTRFS info (device dm-0): relocating block group 119214702592 flags 1
    [44225.843279] BTRFS info (device dm-0): relocating block group 118140960768 flags 1
    [44226.575236] BTRFS info (device dm-0): relocating block group 117067218944 flags 1
    [44226.930918] BTRFS info (device dm-0): relocating block group 95592382464 flags 1


    Can you help me ?










    share|improve this question



























      2












      2








      2








      I cannot shrink btrfs filesystem although there is still data and metadata space left :





      $ sudo btrfs filesystem resize -11G /home;echo $?
      Resize '/home' of '-11G'
      ERROR: unable to resize '/home': No space left on device
      1


      Here are some btrfs filesystem info about /home :



      $ sudo btrfs filesystem df /home | column -t
      Data, single: total=92.01GiB, used=80.68GiB
      System, DUP: total=8.00MiB, used=16.00KiB
      System, single: total=4.00MiB, used=0.00B
      Metadata, DUP: total=1.00GiB, used=631.41MiB
      Metadata, single: total=8.00MiB, used=0.00B
      GlobalReserve, single: total=224.00MiB, used=0.00B
      $ sudo btrfs filesystem show /home
      Label: none uuid: c7ee56a8-ef45-46c8-86d1-13879201a1e7
      Total devices 1 FS bytes used 81.30GiB
      devid 1 size 100.00GiB used 94.04GiB path /dev/mapper/home_VG-home

      $ sudo btrfs filesystem usage -T /home
      Overall:
      Device size: 100.00GiB
      Device allocated: 94.04GiB
      Device unallocated: 5.96GiB
      Device missing: 0.00B
      Used: 81.91GiB
      Free (estimated): 17.29GiB (min: 14.31GiB)
      Data ratio: 1.00
      Metadata ratio: 1.99
      Global reserve: 224.00MiB (used: 0.00B)

      Data Metadata Metadata System System
      Id Path single single DUP single DUP Unallocated
      -- --------- -------- -------- --------- ------- -------- -----------
      1 /dev/dm-0 92.01GiB 8.00MiB 2.00GiB 4.00MiB 16.00MiB 5.96GiB
      -- --------- -------- -------- --------- ------- -------- -----------
      Total 92.01GiB 8.00MiB 1.00GiB 4.00MiB 8.00MiB 5.96GiB
      Used 80.68GiB 0.00B 631.41MiB 0.00B 16.00KiB


      and here the output of dmesg :



      $ dmesg | tail -11
      [44202.411949] BTRFS info (device dm-0): new size for /dev/dm-0 is 97706311680
      [44202.412156] BTRFS info (device dm-0): relocating block group 120288444416 flags 1
      [44208.119721] BTRFS info (device dm-0): relocating block group 119214702592 flags 1
      [44211.611669] BTRFS info (device dm-0): relocating block group 118140960768 flags 1
      [44212.495603] BTRFS info (device dm-0): relocating block group 117067218944 flags 1
      [44213.006830] BTRFS info (device dm-0): relocating block group 95592382464 flags 1
      [44216.613870] BTRFS info (device dm-0): relocating block group 120288444416 flags 1
      [44222.780073] BTRFS info (device dm-0): relocating block group 119214702592 flags 1
      [44225.843279] BTRFS info (device dm-0): relocating block group 118140960768 flags 1
      [44226.575236] BTRFS info (device dm-0): relocating block group 117067218944 flags 1
      [44226.930918] BTRFS info (device dm-0): relocating block group 95592382464 flags 1


      Can you help me ?










      share|improve this question
















      I cannot shrink btrfs filesystem although there is still data and metadata space left :





      $ sudo btrfs filesystem resize -11G /home;echo $?
      Resize '/home' of '-11G'
      ERROR: unable to resize '/home': No space left on device
      1


      Here are some btrfs filesystem info about /home :



      $ sudo btrfs filesystem df /home | column -t
      Data, single: total=92.01GiB, used=80.68GiB
      System, DUP: total=8.00MiB, used=16.00KiB
      System, single: total=4.00MiB, used=0.00B
      Metadata, DUP: total=1.00GiB, used=631.41MiB
      Metadata, single: total=8.00MiB, used=0.00B
      GlobalReserve, single: total=224.00MiB, used=0.00B
      $ sudo btrfs filesystem show /home
      Label: none uuid: c7ee56a8-ef45-46c8-86d1-13879201a1e7
      Total devices 1 FS bytes used 81.30GiB
      devid 1 size 100.00GiB used 94.04GiB path /dev/mapper/home_VG-home

      $ sudo btrfs filesystem usage -T /home
      Overall:
      Device size: 100.00GiB
      Device allocated: 94.04GiB
      Device unallocated: 5.96GiB
      Device missing: 0.00B
      Used: 81.91GiB
      Free (estimated): 17.29GiB (min: 14.31GiB)
      Data ratio: 1.00
      Metadata ratio: 1.99
      Global reserve: 224.00MiB (used: 0.00B)

      Data Metadata Metadata System System
      Id Path single single DUP single DUP Unallocated
      -- --------- -------- -------- --------- ------- -------- -----------
      1 /dev/dm-0 92.01GiB 8.00MiB 2.00GiB 4.00MiB 16.00MiB 5.96GiB
      -- --------- -------- -------- --------- ------- -------- -----------
      Total 92.01GiB 8.00MiB 1.00GiB 4.00MiB 8.00MiB 5.96GiB
      Used 80.68GiB 0.00B 631.41MiB 0.00B 16.00KiB


      and here the output of dmesg :



      $ dmesg | tail -11
      [44202.411949] BTRFS info (device dm-0): new size for /dev/dm-0 is 97706311680
      [44202.412156] BTRFS info (device dm-0): relocating block group 120288444416 flags 1
      [44208.119721] BTRFS info (device dm-0): relocating block group 119214702592 flags 1
      [44211.611669] BTRFS info (device dm-0): relocating block group 118140960768 flags 1
      [44212.495603] BTRFS info (device dm-0): relocating block group 117067218944 flags 1
      [44213.006830] BTRFS info (device dm-0): relocating block group 95592382464 flags 1
      [44216.613870] BTRFS info (device dm-0): relocating block group 120288444416 flags 1
      [44222.780073] BTRFS info (device dm-0): relocating block group 119214702592 flags 1
      [44225.843279] BTRFS info (device dm-0): relocating block group 118140960768 flags 1
      [44226.575236] BTRFS info (device dm-0): relocating block group 117067218944 flags 1
      [44226.930918] BTRFS info (device dm-0): relocating block group 95592382464 flags 1


      Can you help me ?







      filesystems btrfs






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 4 hours ago







      SebMa

















      asked 7 hours ago









      SebMaSebMa

      1366




      1366






















          1 Answer
          1






          active

          oldest

          votes


















          2














          You're requesting the volume to shrink by 11GB, yet you only have about 6GB unallocated.



          You can more efficiently use allocated extents by rebalancing the volume. Executing a command similar to btrfs balance start /home will start that process, and it may take some time to complete.



          But I don't know if that will free up enough for a large amount of shrinkage.






          share|improve this answer
























          • I though I add 14.31GiB free according to this : Free (estimated): 17.29GiB (min: 14.31GiB)

            – SebMa
            1 hour ago






          • 1





            But you're requesting a volume change, which deals with allocated extents rather than how they're used. You could have almost the entire volume "free", but if the whole thing is "allocated" you can't shrink it. Running a rebalance will reallocate used data in a more efficient way.

            – Spooler
            49 mins ago











          • Ok, thanks bro. I'll do this tomorrow 'cause it's 20 to 4 (A.M) in France.

            – SebMa
            41 mins ago












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "2"
          };
          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%2fserverfault.com%2fquestions%2f960860%2fcannot-shrink-btrfs-filesystem-although-there-is-still-data-and-metadata-space-l%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









          2














          You're requesting the volume to shrink by 11GB, yet you only have about 6GB unallocated.



          You can more efficiently use allocated extents by rebalancing the volume. Executing a command similar to btrfs balance start /home will start that process, and it may take some time to complete.



          But I don't know if that will free up enough for a large amount of shrinkage.






          share|improve this answer
























          • I though I add 14.31GiB free according to this : Free (estimated): 17.29GiB (min: 14.31GiB)

            – SebMa
            1 hour ago






          • 1





            But you're requesting a volume change, which deals with allocated extents rather than how they're used. You could have almost the entire volume "free", but if the whole thing is "allocated" you can't shrink it. Running a rebalance will reallocate used data in a more efficient way.

            – Spooler
            49 mins ago











          • Ok, thanks bro. I'll do this tomorrow 'cause it's 20 to 4 (A.M) in France.

            – SebMa
            41 mins ago
















          2














          You're requesting the volume to shrink by 11GB, yet you only have about 6GB unallocated.



          You can more efficiently use allocated extents by rebalancing the volume. Executing a command similar to btrfs balance start /home will start that process, and it may take some time to complete.



          But I don't know if that will free up enough for a large amount of shrinkage.






          share|improve this answer
























          • I though I add 14.31GiB free according to this : Free (estimated): 17.29GiB (min: 14.31GiB)

            – SebMa
            1 hour ago






          • 1





            But you're requesting a volume change, which deals with allocated extents rather than how they're used. You could have almost the entire volume "free", but if the whole thing is "allocated" you can't shrink it. Running a rebalance will reallocate used data in a more efficient way.

            – Spooler
            49 mins ago











          • Ok, thanks bro. I'll do this tomorrow 'cause it's 20 to 4 (A.M) in France.

            – SebMa
            41 mins ago














          2












          2








          2







          You're requesting the volume to shrink by 11GB, yet you only have about 6GB unallocated.



          You can more efficiently use allocated extents by rebalancing the volume. Executing a command similar to btrfs balance start /home will start that process, and it may take some time to complete.



          But I don't know if that will free up enough for a large amount of shrinkage.






          share|improve this answer













          You're requesting the volume to shrink by 11GB, yet you only have about 6GB unallocated.



          You can more efficiently use allocated extents by rebalancing the volume. Executing a command similar to btrfs balance start /home will start that process, and it may take some time to complete.



          But I don't know if that will free up enough for a large amount of shrinkage.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 1 hour ago









          SpoolerSpooler

          6,0591127




          6,0591127













          • I though I add 14.31GiB free according to this : Free (estimated): 17.29GiB (min: 14.31GiB)

            – SebMa
            1 hour ago






          • 1





            But you're requesting a volume change, which deals with allocated extents rather than how they're used. You could have almost the entire volume "free", but if the whole thing is "allocated" you can't shrink it. Running a rebalance will reallocate used data in a more efficient way.

            – Spooler
            49 mins ago











          • Ok, thanks bro. I'll do this tomorrow 'cause it's 20 to 4 (A.M) in France.

            – SebMa
            41 mins ago



















          • I though I add 14.31GiB free according to this : Free (estimated): 17.29GiB (min: 14.31GiB)

            – SebMa
            1 hour ago






          • 1





            But you're requesting a volume change, which deals with allocated extents rather than how they're used. You could have almost the entire volume "free", but if the whole thing is "allocated" you can't shrink it. Running a rebalance will reallocate used data in a more efficient way.

            – Spooler
            49 mins ago











          • Ok, thanks bro. I'll do this tomorrow 'cause it's 20 to 4 (A.M) in France.

            – SebMa
            41 mins ago

















          I though I add 14.31GiB free according to this : Free (estimated): 17.29GiB (min: 14.31GiB)

          – SebMa
          1 hour ago





          I though I add 14.31GiB free according to this : Free (estimated): 17.29GiB (min: 14.31GiB)

          – SebMa
          1 hour ago




          1




          1





          But you're requesting a volume change, which deals with allocated extents rather than how they're used. You could have almost the entire volume "free", but if the whole thing is "allocated" you can't shrink it. Running a rebalance will reallocate used data in a more efficient way.

          – Spooler
          49 mins ago





          But you're requesting a volume change, which deals with allocated extents rather than how they're used. You could have almost the entire volume "free", but if the whole thing is "allocated" you can't shrink it. Running a rebalance will reallocate used data in a more efficient way.

          – Spooler
          49 mins ago













          Ok, thanks bro. I'll do this tomorrow 'cause it's 20 to 4 (A.M) in France.

          – SebMa
          41 mins ago





          Ok, thanks bro. I'll do this tomorrow 'cause it's 20 to 4 (A.M) in France.

          – SebMa
          41 mins ago


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Server Fault!


          • 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%2fserverfault.com%2fquestions%2f960860%2fcannot-shrink-btrfs-filesystem-although-there-is-still-data-and-metadata-space-l%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

          ORA-01691 (unable to extend lob segment) even though my tablespace has AUTOEXTEND onORA-01692: unable to...

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          Circunscripción electoral de Guipúzcoa Referencias Menú de navegaciónLas claves del sistema electoral en...