On Mon 01 May 2023 at 23:24:56 (-0400), Timothy M Butterworth wrote: > On Mon, May 1, 2023 at 10:45 PM Rick Thomas <rick.tho...@pobox.com> wrote: > > On Mon, May 1, 2023, at 11:14 AM, Bret Busby wrote: > > > On 2/5/23 02:06, David Christensen wrote: > > >> On 5/1/23 06:51, Bonno Bloksma wrote: > > >>> The cause seems to be the folder /usr/lib/modules# > > >>> linams:/usr/lib/modules# du * -sh > > >>> 4.7M 5.10.0-10-amd64 > > >>> 4.7M 5.10.0-11-amd64 > > >>> 4.7M 5.10.0-12-amd64 > > >>> 4.7M 5.10.0-13-amd64 > > >>> 4.7M 5.10.0-15-amd64 > > >>> 4.7M 5.10.0-16-amd64 > > >>> 309M 5.10.0-18-amd64 > > >>> 309M 5.10.0-19-amd64 > > >>> 309M 5.10.0-20-amd64 > > >>> 309M 5.10.0-21-amd64 > > >>> 309M 5.10.0-22-amd64 > > >>> 4.7M 5.10.0-7-amd64 > > >>> 4.7M 5.10.0-8-amd64 > > >>> 4.7M 5.10.0-9-amd64 > > >>> > > Did anyone else notice the massive jump in file size here? 4.7M to 309M is > a huge increase in file size!
4.7MB is the size of the modules.* that are created during installation, as I mentioned in my post. These are deleted by purge but not by remove, whereas: $ du -sh /lib/modules/5.10.0-22-amd64/ 309M /lib/modules/5.10.0-22-amd64/ $ is the modules themselves, awaiting deletion. (Actually, this particular listing is my live kernel.) Host linams is the most burdened one, with five sets of modules. I'm assuming that the kernels/initrds have gone from /boot. If all five are still there, then the good news is that my first post doesn't apply, and they've simply forgotten to remove the 1st, 2nd and 3rd oldest kernels (and it's best to use purge for less clutter). > > > Have you tried running also > > > apt autoclean I thought that just cleared /var/cache/apt/archives/. > > > and > > > apt purge I've never tried that without a package name. What does it do? Cheers, David.
