Run out of space when updating

I am on KDE. I expirienced for the first time I use Manjaro a very strange issue. I had 15GB free space available. Download was about 2GB and estimation after instalation about 6,5GB. But when instalation was going on system run out of space. I reverted changes from backup but this happend again and again. Maybe some packages have problem with being unpacked and multiply themeselves…

Last time it happend the package processed was oxygen icons.

Maybe data written to journalctl cause such problem…
I am on BTRFS.

df -h

dev             3,9G     0  3,9G   0% /dev
run             3,9G  9,4M  3,9G   1% /run
/dev/sda1        56G   41G   16G  72% /
tmpfs           3,9G     0  3,9G   0% /dev/shm
/dev/sda1        56G   41G   16G  72% /home
/dev/sda1        56G   41G   16G  72% /home/user/Data
/dev/sda1        56G   41G   16G  72% /swap
tmpfs           3,9G  4,0K  3,9G   1% /tmp
tmpfs           787M   60K  786M   1% /run/user/1000


sudo btrfs filesystem usage /
 
Overall:
    Device size:                  55.90GiB
    Device allocated:             55.90GiB
    Device unallocated:              0.00B
    Device missing:                  0.00B
    Device slack:                    0.00B
    Used:                         39.97GiB
    Free (estimated):             15.66GiB      (min: 15.66GiB)
    Free (statfs, df):            15.66GiB
    Data ratio:                       1.00
    Metadata ratio:                   1.00
    Global reserve:               90.56MiB      (used: 0.00B)
    Multiple profiles:                  no

Data,single: Size:54.88GiB, Used:39.23GiB (71.47%)
   /dev/sda1      54.88GiB

Metadata,single: Size:1.01GiB, Used:760.11MiB (73.65%)
   /dev/sda1       1.01GiB

System,single: Size:4.00MiB, Used:16.00KiB (0.39%)
   /dev/sda1       4.00MiB

Unallocated:
   /dev/sda1         0.00B

Have you tried cleaning out your package cache?

sudo paccache -rvk0
1 Like
sudo paccache -rvk0
==> no candidate packages found for pruning

I was doing update in TTY.

Well, something is eating up your storage space. Maybe you need to prune some stuff. If you have any Snaps, FlatPaks or AppImages, those take up a lot of storage. :man_shrugging:

I deleted bakup and having 22GB free space I was able to update. But having 10Gb free space when doing recommended

pamac build $(pacman -Qoq /usr/lib/python3.10)

I ended up with the same problem. It is a strange inconsistency between below command outputs:

sudo btrfs filesystem usage /

Overall:
    Device size:                  55.90GiB
    Device allocated:             55.90GiB
    Device unallocated:              0.00B
    Device missing:                  0.00B
    Device slack:                    0.00B
    Used:                         46.12GiB
    Free (estimated):              9.68GiB      (min: 9.68GiB)
    Free (statfs, df):               0.00B
    Data ratio:                       1.00
    Metadata ratio:                   1.00
    Global reserve:               89.06MiB      (used: 0.00B)
    Multiple profiles:                  no

Data,single: Size:54.88GiB, Used:45.20GiB (82.36%)
   /dev/sda1      54.88GiB

Metadata,single: Size:1.01GiB, Used:940.14MiB (91.10%)
   /dev/sda1       1.01GiB

System,single: Size:4.00MiB, Used:16.00KiB (0.39%)
   /dev/sda1       4.00MiB

Unallocated:
   /dev/sda1         0.00B
[user@user-pc ~]$ df -h
System plików  rozm. użyte dost. %uż. zamont. na
dev             3,9G     0  3,9G   0% /dev
run             3,9G  9,4M  3,9G   1% /run
/dev/sda1        56G   47G     0 100% /
tmpfs           3,9G     0  3,9G   0% /dev/shm
/dev/sda1        56G   47G     0 100% /homea
/dev/sda1        56G   47G     0 100% /home/user/Data
/dev/sda1        56G   47G     0 100% /swap
tmpfs           3,9G  4,0K  3,9G   1% /tmp
tmpfs           787M   68K  786M   1% /run/user/1000
[user@user-pc ~]$

And dolphin shows free 0 B. But I can still browse internet.

I have no idea what can cause this problem.

Maybe this is a btrfs thing or something else … but … am I the only one that thinks this looks bonkers ?

2 Likes

You probably have (too) many btrfs snapshots. Also, btrfs uses compression by default, and therefore, unpacking the updates and recompressing them requires that there be some additional free space.


No, this is normal for btrfs if you’re using subvolumes.

Unlike in zfs, btrfs subvolumes are not block devices, and so the block device associated with a subvolume in the output of df is the one that holds the entire btrfs filesystem. The btrfs command does have its own version of df built in, though.

man btrfs-filesystem

:wink:

You find good Information about Btrfs in the wiki

please show

sudo btrfs subvolume list /

But first of all

You need to examine what files are filling up your hard drive when updating
:footprints:

1 Like

My thought exactly.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.