Dust is a rewrite of du (in rust obviously) that visualizes your directory tree and what percentage each file takes up. But it only prints as many files fit in your terminal height, so you see only the largest files. It’s been a better experience that du, which isn’t always easy to navigate to find big files (or atleast I’m not good at it.)
Anyway, found a log file at .local/state/nvim/log that was 70gb. I deleted it. Hope it doesn’t bite me. Been pushing around 95% of disk space for a while so this was a huge win 👍
You must log in or register to comment.
I think something might be wrong with your Neovim if it aggregated 70 gigs of log files.
don’t worry, they’ve just been using neovim for 700 years, it’ll be alright
So I found out that qbittorrent generates errors in a log whenever it tries to write to a disk that is full…
Everytime my disk was full I would clear out some old torrents, then all the pending log entries would write and the disk would be full again. The log was well over 50gb by the time I figured out that i’m an idiot. Hooray for having dedicated machines.
I once did something even dumber. When I was new to Linux and the CLI, I added a recursive line to my shell config that would add it self to the shell config. So I pretty much had exponential growth of my shell config and my shell would take ~20 seconds to start up before I found the broken code snippet.
ncdu is the best utility for this type of thing. I use it all the time.
Try dua. It’s like ncdu but uses multiple threads so it’s a lot faster., especially on SSDs.
