BTRFS Shrink: No Space on Disk? [duplicate]





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0
















This question already has an answer here:




  • How can I safely resize (shrink) a BTRFS partition?

    2 answers




I'm trying to shrink my btrfs 900Gib HDD down to 500Gib so that I can transfer it using clonezilla to my new 500 Gib SSD.



I thought that I could just shrink down the partition using gparted, but it fails with this error:



GParted 0.30.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2
Shrink /dev/sda2 from 931.01 GiB to 406.71 GiB 01:20:34 ( ERROR )

calibrate /dev/sda2 00:00:01 ( SUCCESS )

path: /dev/sda2 (partition)
start: 1050624
end: 1953519615
size: 1952468992 (931.01 GiB)
shrink file system 01:20:33 ( ERROR )

btrfs filesystem resize 1:426467328K '/mnt' 01:20:33 ( ERROR )

Resize '/mnt' of '1:426467328K'
ERROR: unable to resize '/mnt': No space left on device

========================================


This also occurs when I try and resize from 470GiB -> 433GiB. I don't believe that it can run out of space on the disk as there is 497GiB.
Gparted



This was performed on an unencrypted home folder from the kubuntu 18.04.01 live usb.



EDIT 0: Output of sudo filesystem show /mnt (Which is where I have



/dev/sda2 mounted)
kubuntu@kubuntu:~$ sudo btrfs filesystem show /mnt
Label: none uuid: 029c3c88-8edb-4da0-a741-5d912950e2e1
Total devices 1 FS bytes used 406.61GiB
devid 1 size 473.68GiB used 461.10GiB path /dev/sda2









share|improve this question















marked as duplicate by karel, Eric Carvalho, Charles Green, Elder Geek, dessert Feb 20 at 20:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.



















  • As you attempting to resize a partition whilst in use?

    – guiverc
    Feb 16 at 3:11











  • @guiverc That's what the picture is from, but that doesn't explain why it doesn't work on the live USB. I'll grab a screenshot of the error from there and post it here.

    – Sarah Szabo
    Feb 16 at 4:19











  • The 'live' image uses a '/' created on boot in memory. It's a fixed size that cannot be changed during the session, and I'm better the 'btrfs' resize requires more memory than the live / (fs) has. You may need to resize using an installed system (with the partition unmounted of course).

    – guiverc
    Feb 16 at 4:20













  • s/better/betting/ (in my last comment)

    – guiverc
    Feb 16 at 4:28













  • @guiverc When you say unmounted, do you mean unmount /dev/sda2? Is that even possible when xServer is running? Or would I have to drop to console before X boots and use the btrfs filesystem resize command from there? Is there any way to use gparted there?

    – Sarah Szabo
    Feb 16 at 5:50


















0
















This question already has an answer here:




  • How can I safely resize (shrink) a BTRFS partition?

    2 answers




I'm trying to shrink my btrfs 900Gib HDD down to 500Gib so that I can transfer it using clonezilla to my new 500 Gib SSD.



I thought that I could just shrink down the partition using gparted, but it fails with this error:



GParted 0.30.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2
Shrink /dev/sda2 from 931.01 GiB to 406.71 GiB 01:20:34 ( ERROR )

calibrate /dev/sda2 00:00:01 ( SUCCESS )

path: /dev/sda2 (partition)
start: 1050624
end: 1953519615
size: 1952468992 (931.01 GiB)
shrink file system 01:20:33 ( ERROR )

btrfs filesystem resize 1:426467328K '/mnt' 01:20:33 ( ERROR )

Resize '/mnt' of '1:426467328K'
ERROR: unable to resize '/mnt': No space left on device

========================================


This also occurs when I try and resize from 470GiB -> 433GiB. I don't believe that it can run out of space on the disk as there is 497GiB.
Gparted



This was performed on an unencrypted home folder from the kubuntu 18.04.01 live usb.



EDIT 0: Output of sudo filesystem show /mnt (Which is where I have



/dev/sda2 mounted)
kubuntu@kubuntu:~$ sudo btrfs filesystem show /mnt
Label: none uuid: 029c3c88-8edb-4da0-a741-5d912950e2e1
Total devices 1 FS bytes used 406.61GiB
devid 1 size 473.68GiB used 461.10GiB path /dev/sda2









share|improve this question















marked as duplicate by karel, Eric Carvalho, Charles Green, Elder Geek, dessert Feb 20 at 20:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.



















  • As you attempting to resize a partition whilst in use?

    – guiverc
    Feb 16 at 3:11











  • @guiverc That's what the picture is from, but that doesn't explain why it doesn't work on the live USB. I'll grab a screenshot of the error from there and post it here.

    – Sarah Szabo
    Feb 16 at 4:19











  • The 'live' image uses a '/' created on boot in memory. It's a fixed size that cannot be changed during the session, and I'm better the 'btrfs' resize requires more memory than the live / (fs) has. You may need to resize using an installed system (with the partition unmounted of course).

    – guiverc
    Feb 16 at 4:20













  • s/better/betting/ (in my last comment)

    – guiverc
    Feb 16 at 4:28













  • @guiverc When you say unmounted, do you mean unmount /dev/sda2? Is that even possible when xServer is running? Or would I have to drop to console before X boots and use the btrfs filesystem resize command from there? Is there any way to use gparted there?

    – Sarah Szabo
    Feb 16 at 5:50














0












0








0









This question already has an answer here:




  • How can I safely resize (shrink) a BTRFS partition?

    2 answers




I'm trying to shrink my btrfs 900Gib HDD down to 500Gib so that I can transfer it using clonezilla to my new 500 Gib SSD.



I thought that I could just shrink down the partition using gparted, but it fails with this error:



GParted 0.30.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2
Shrink /dev/sda2 from 931.01 GiB to 406.71 GiB 01:20:34 ( ERROR )

calibrate /dev/sda2 00:00:01 ( SUCCESS )

path: /dev/sda2 (partition)
start: 1050624
end: 1953519615
size: 1952468992 (931.01 GiB)
shrink file system 01:20:33 ( ERROR )

btrfs filesystem resize 1:426467328K '/mnt' 01:20:33 ( ERROR )

Resize '/mnt' of '1:426467328K'
ERROR: unable to resize '/mnt': No space left on device

========================================


This also occurs when I try and resize from 470GiB -> 433GiB. I don't believe that it can run out of space on the disk as there is 497GiB.
Gparted



This was performed on an unencrypted home folder from the kubuntu 18.04.01 live usb.



EDIT 0: Output of sudo filesystem show /mnt (Which is where I have



/dev/sda2 mounted)
kubuntu@kubuntu:~$ sudo btrfs filesystem show /mnt
Label: none uuid: 029c3c88-8edb-4da0-a741-5d912950e2e1
Total devices 1 FS bytes used 406.61GiB
devid 1 size 473.68GiB used 461.10GiB path /dev/sda2









share|improve this question

















This question already has an answer here:




  • How can I safely resize (shrink) a BTRFS partition?

    2 answers




I'm trying to shrink my btrfs 900Gib HDD down to 500Gib so that I can transfer it using clonezilla to my new 500 Gib SSD.



I thought that I could just shrink down the partition using gparted, but it fails with this error:



GParted 0.30.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2
Shrink /dev/sda2 from 931.01 GiB to 406.71 GiB 01:20:34 ( ERROR )

calibrate /dev/sda2 00:00:01 ( SUCCESS )

path: /dev/sda2 (partition)
start: 1050624
end: 1953519615
size: 1952468992 (931.01 GiB)
shrink file system 01:20:33 ( ERROR )

btrfs filesystem resize 1:426467328K '/mnt' 01:20:33 ( ERROR )

Resize '/mnt' of '1:426467328K'
ERROR: unable to resize '/mnt': No space left on device

========================================


This also occurs when I try and resize from 470GiB -> 433GiB. I don't believe that it can run out of space on the disk as there is 497GiB.
Gparted



This was performed on an unencrypted home folder from the kubuntu 18.04.01 live usb.



EDIT 0: Output of sudo filesystem show /mnt (Which is where I have



/dev/sda2 mounted)
kubuntu@kubuntu:~$ sudo btrfs filesystem show /mnt
Label: none uuid: 029c3c88-8edb-4da0-a741-5d912950e2e1
Total devices 1 FS bytes used 406.61GiB
devid 1 size 473.68GiB used 461.10GiB path /dev/sda2




This question already has an answer here:




  • How can I safely resize (shrink) a BTRFS partition?

    2 answers








partitioning filesystem gparted btrfs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 17 at 18:42







Sarah Szabo

















asked Feb 16 at 2:57









Sarah SzaboSarah Szabo

413921




413921




marked as duplicate by karel, Eric Carvalho, Charles Green, Elder Geek, dessert Feb 20 at 20:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.









marked as duplicate by karel, Eric Carvalho, Charles Green, Elder Geek, dessert Feb 20 at 20:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • As you attempting to resize a partition whilst in use?

    – guiverc
    Feb 16 at 3:11











  • @guiverc That's what the picture is from, but that doesn't explain why it doesn't work on the live USB. I'll grab a screenshot of the error from there and post it here.

    – Sarah Szabo
    Feb 16 at 4:19











  • The 'live' image uses a '/' created on boot in memory. It's a fixed size that cannot be changed during the session, and I'm better the 'btrfs' resize requires more memory than the live / (fs) has. You may need to resize using an installed system (with the partition unmounted of course).

    – guiverc
    Feb 16 at 4:20













  • s/better/betting/ (in my last comment)

    – guiverc
    Feb 16 at 4:28













  • @guiverc When you say unmounted, do you mean unmount /dev/sda2? Is that even possible when xServer is running? Or would I have to drop to console before X boots and use the btrfs filesystem resize command from there? Is there any way to use gparted there?

    – Sarah Szabo
    Feb 16 at 5:50



















  • As you attempting to resize a partition whilst in use?

    – guiverc
    Feb 16 at 3:11











  • @guiverc That's what the picture is from, but that doesn't explain why it doesn't work on the live USB. I'll grab a screenshot of the error from there and post it here.

    – Sarah Szabo
    Feb 16 at 4:19











  • The 'live' image uses a '/' created on boot in memory. It's a fixed size that cannot be changed during the session, and I'm better the 'btrfs' resize requires more memory than the live / (fs) has. You may need to resize using an installed system (with the partition unmounted of course).

    – guiverc
    Feb 16 at 4:20













  • s/better/betting/ (in my last comment)

    – guiverc
    Feb 16 at 4:28













  • @guiverc When you say unmounted, do you mean unmount /dev/sda2? Is that even possible when xServer is running? Or would I have to drop to console before X boots and use the btrfs filesystem resize command from there? Is there any way to use gparted there?

    – Sarah Szabo
    Feb 16 at 5:50

















As you attempting to resize a partition whilst in use?

– guiverc
Feb 16 at 3:11





As you attempting to resize a partition whilst in use?

– guiverc
Feb 16 at 3:11













@guiverc That's what the picture is from, but that doesn't explain why it doesn't work on the live USB. I'll grab a screenshot of the error from there and post it here.

– Sarah Szabo
Feb 16 at 4:19





@guiverc That's what the picture is from, but that doesn't explain why it doesn't work on the live USB. I'll grab a screenshot of the error from there and post it here.

– Sarah Szabo
Feb 16 at 4:19













The 'live' image uses a '/' created on boot in memory. It's a fixed size that cannot be changed during the session, and I'm better the 'btrfs' resize requires more memory than the live / (fs) has. You may need to resize using an installed system (with the partition unmounted of course).

– guiverc
Feb 16 at 4:20







The 'live' image uses a '/' created on boot in memory. It's a fixed size that cannot be changed during the session, and I'm better the 'btrfs' resize requires more memory than the live / (fs) has. You may need to resize using an installed system (with the partition unmounted of course).

– guiverc
Feb 16 at 4:20















s/better/betting/ (in my last comment)

– guiverc
Feb 16 at 4:28







s/better/betting/ (in my last comment)

– guiverc
Feb 16 at 4:28















@guiverc When you say unmounted, do you mean unmount /dev/sda2? Is that even possible when xServer is running? Or would I have to drop to console before X boots and use the btrfs filesystem resize command from there? Is there any way to use gparted there?

– Sarah Szabo
Feb 16 at 5:50





@guiverc When you say unmounted, do you mean unmount /dev/sda2? Is that even possible when xServer is running? Or would I have to drop to console before X boots and use the btrfs filesystem resize command from there? Is there any way to use gparted there?

– Sarah Szabo
Feb 16 at 5:50










1 Answer
1






active

oldest

votes


















0














I found that there were some old Timeshift snapshots. I deleted the snapshots on /dev/sda2 and was able to compress the disk.



It escaped my noticed because I had long since removed and purged timeshift, but the snapshots had remained and bloated due to all the movement on the filesystem.






share|improve this answer






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I found that there were some old Timeshift snapshots. I deleted the snapshots on /dev/sda2 and was able to compress the disk.



    It escaped my noticed because I had long since removed and purged timeshift, but the snapshots had remained and bloated due to all the movement on the filesystem.






    share|improve this answer




























      0














      I found that there were some old Timeshift snapshots. I deleted the snapshots on /dev/sda2 and was able to compress the disk.



      It escaped my noticed because I had long since removed and purged timeshift, but the snapshots had remained and bloated due to all the movement on the filesystem.






      share|improve this answer


























        0












        0








        0







        I found that there were some old Timeshift snapshots. I deleted the snapshots on /dev/sda2 and was able to compress the disk.



        It escaped my noticed because I had long since removed and purged timeshift, but the snapshots had remained and bloated due to all the movement on the filesystem.






        share|improve this answer













        I found that there were some old Timeshift snapshots. I deleted the snapshots on /dev/sda2 and was able to compress the disk.



        It escaped my noticed because I had long since removed and purged timeshift, but the snapshots had remained and bloated due to all the movement on the filesystem.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 19 at 2:58









        Sarah SzaboSarah Szabo

        413921




        413921















            Popular posts from this blog

            Human spaceflight

            Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

            張江高科駅