Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have recently installed Arch Linux and found that I am eating away at a lot of memory relatively quickly. For whatever reason I have already used 17GB in just about 2 weeks. I do not have a great deal of software installed so I am led to believe that all of the old packages are maintained somewhere.

To support this, I have noticed that if I installed a package, remove that package, and then re-install it that pacman merely unpacks and re-installs the software without having to re-download it.

After I installed my base system, before extra software, I used about 2GB or so maybe. I have since only installed Matlab, Skype, Wine, and a few other small programs. Of course I have also installed missing libraries and the like, but not nearly 15GB worth.

Am I completely wrong here or does Arch never delete old packages when downloading/upgrading to new versions?

If so, how do I delete these un-used packages?

Also, when I remove installed packages I use pacman -R ...

share|improve this question
It's probably a good idea to set up paccache as a regular cron or systemd job. – Sparhawk Jun 17 '14 at 7:31

No, pacman doesn't remove old packages from your cache (/var/cache/pacman/pkg) so, over time, it can fill up.

You can adopt two approaches to clearing the cache: the brute force one with pacman -Sc:

-c, --clean
Remove packages that are no longer installed from the cache as well as currently unused sync databases to free up disk space. When pacman downloads packages, it saves them in a cache directory. In addition, databases are saved for every sync DB you download from, and are not deleted even if they are removed from the configuration file pacman.conf(5). Use one --clean switch to only remove packages that are no longer installed; use two to remove all files from the cache. In both cases, you will have a yes or no option to remove packages and/or unused downloaded databases.

Or, for a more nuanced approach, you can use one of the utilities that ships with pacman, paccache:

paccache is a flexible pacman cache cleaning utility, which has numerous options to help control how much, and what, is deleted from any directory containing pacman package tarballs.

By default, paccache will remove all but the last three versions of an installed package, but you can change this number with the -k, --keep switch. There is also a -d, --dryrun switch to preview your changes. See paccache --help for all the switches.

Aside: pacman ships with a number of helpful tools, it is worth looking though them all and gaining an understanding of how they work and can make running Arch much easier. You can see the full list with:

pacman -Ql pacman | awk -F"[/ ]" '/\/usr\/bin/ {print $5}'
share|improve this answer
jasonwryan said it :) Also be really careful with the double --clean switch: that forbids easily reverting to the working package, in case any issue happens with the latest version (eg new package relies on an older lib or Python release; same with hardware and latest kernel). I find setting the pacman cache elsewhere than / a much better solution (just set the path in /etc/pacman.conf). – lliseil Jul 28 '15 at 16:19

Your package cache is in /var/cache/pacman/pkg/.


paccache -d

To do a -dryrun and see what a run of that utility might remove when you next do:

paccache -r

To remove cached packages. 17gbs does sound steep. Make sure you haven't got some run-away logs. Do:

du -h /var/log

Or even just:

du -h /var

For a more general idea of what's going on.

share|improve this answer

pacman -Scc does what you're asking, but it's not recommended. From the Wiki

It is also possible to completely empty the cache folder with pacman -Scc, but doing it is considered bad practice, as, in addition to the above, it also prevents from reinstalling a package directly from the cache folder in case of need, thus forcing to redownload it. You should never use it unless there is a desperate need for more disk space.

As an aside, when I uninstall packages, I prefer to use pacman -Rnsc, since it also removes package dependencies as well as packages that depend on this one. As always, read carefully which packages are being removed, since you could very easily leave our system in an unusable state.

share|improve this answer
That's cool - so it's equivalent to rm /var/cache/pacman/pkg/* then? Or - it as at least by default, I guess. I've relocated my pkg cache to /tmp on most machines a long time ago and let squid handle a single central cache at the router. Not as easy as pacman -Scc though. – mikeserv Jun 16 '14 at 4:27
@mikeserv A central Pacman package cache at your router? How did you set it up, I like the sound of it since I have both an Arch desktop and laptop. – Shrike Feb 13 at 9:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.