Cleaning the nix store: Difference between revisions

From NixOS Wiki
imported>Mic92
No edit summary
imported>Makefu
add more references and a command to find result files
Line 1: Line 1:
Sometimes your store fills up the disk, but a simple <syntaxHighlight>nix-store --gc</syntaxHighlight> does not seem to clean all that much.
Sometimes your store fills up the disk, but a simple <syntaxHighlight>nix-store --gc</syntaxHighlight> does not seem to clean all that much.


This usually means that you have some garbage collection roots that keep old versions of nixpkgs around.
This usually means that you have some old collection roots that keep old versions of nixpkgs around.


There is multiple tools that can help with discovering these gc roots:
Sometimes <code>result</code> files created by an ad-hoc <code>nix-build</code> bind a lot of resources, these can be found by running:
<syntaxHighlight>
nix-store --gc --print-roots | egrep -v "^(/nix/var|/run/\w+-system|\{memory|/proc)"
</syntaxHighlight>
 
Additional Resources about cleaning up the nix-store are:
 
* https://matthewrhone.dev/nixos-package-guide#cleanup-old-packages-user-wide
* https://nixos.wiki/wiki/Storage_optimization
* https://old.reddit.com/r/NixOS/comments/8m1n3d/taking_out_the_trash/
 
There is multiple tools that can help with discovering gc roots and calculate the disk size:


* https://github.com/symphorien/nix-du
* https://github.com/symphorien/nix-du

Revision as of 09:51, 15 February 2021

Sometimes your store fills up the disk, but a simple

nix-store --gc

does not seem to clean all that much.

This usually means that you have some old collection roots that keep old versions of nixpkgs around.

Sometimes result files created by an ad-hoc nix-build bind a lot of resources, these can be found by running:

nix-store --gc --print-roots | egrep -v "^(/nix/var|/run/\w+-system|\{memory|/proc)"

Additional Resources about cleaning up the nix-store are:

There is multiple tools that can help with discovering gc roots and calculate the disk size: