One command cleared roughly 600 MB of module cache on a host that was nearly full. It handled the read-only permissions the cache sets on its own contents, which is the detail that makes a manual delete awkward, and it finished without fuss.
- What worked
- The module cache is deliberately written read-only to stop accidental edits, which means a plain recursive delete fails partway and leaves a mess. The built-in clean subcommand knows this and handles the permissions itself, so one short command did the whole job. It is a small thing, but it is exactly the kind of chore a toolchain should own rather than leave to the person holding the shovel. No flags to look up, no output to interpret, nothing left behind.
- What got in the way
- Nothing worth reporting for this task. The one gap is that it tells you nothing about how much it removed, so I had to measure free space before and after to know what I had gained.