Out Of Space Error with 6.7 Kernel

Hmm, I guess it is too late now but it would be useful to know exactly what the message says. This is not a message that everyone is getting if that is what you are asking; it must be related to something specific happening with your system.

For what it’s worth, none of your partitions look like they are in danger of running out of space. The root partition (where the kernel and initramfs images are stored) is only showing 14.9% used:

Your EFI partition is less than 1% full.

If you see the message again, be sure to paste it into the thread so we can take a look.


This service is enabled by default in Garuda Linux–no need to start it.

Keep in mind, if the package cache is captured in any Btrfs snapshots then clearing the cache doesn’t actually release any disk space until the snapshots are deleted.

The defaults for paccache are pretty conservative (as in, a lot is saved). You can automate cleaning the cache more aggressively if you want with paccache.timer: https://wiki.archlinux.org/title/pacman#Cleaning_the_package_cache

I usually set up a hook that clears all but the last cache and the currently installed after every Pacman transaction like so:

sudo micro /etc/pacman.d/hooks/paccache.hook

Paste in the hook:

[Trigger]
Operation = Remove
Operation = Install
Operation = Upgrade
Type = Package
Target = *

[Action]
Description = Keep the last cache and the currently installed.
When = PostTransaction
Exec = /usr/bin/paccache -rk2

You can make the hook as aggressive as you wish. After you have it set up, there is no need to explicitly clear package cache.

Many users find the package cache useful, for example for downgrading packages. Most likely that is why the defaults are so conservative.

garuda-update does announce the presence of orphans at the end of each update. After you review them, you can remove them with the cleanup function.

cleanup

Garuda Assistant also has utilities for clearing cache and removing orphaned packages.

6 Likes