dust VS btdu

Try using dust https://github.com/bootandy/dust

Folks open to using gdu might like to try dust (6k stars), or even erdtree (1.4k stars) which is too recent to show up on lists like this and still a bit behind on stars. A lot of people seem to use starship (33k stars) though I'm personally oldschool on prompts. There are many other items on that list I'm not motivated to check.

The first thought I had was to use rayon for this. And looking at some prior art that does pretty much the exact same thing, it does indeed use rayon.

The dust CLI command (made with Rust) can do this too.

How does this compare to dust?

Happened to me this morning, something filled up my drive in minutes. I used dust[1] to look for large files while it was happening but knowing what was doing it would've been a big help.

[1] https://github.com/bootandy/dust

dust is also really nice.

Hello. I have a 2 TB nvme mounted as a subvol that contains dockervols. I recently noticed this discrepancy df -h | grep nvme0n1p1 /dev/nvme0n1p1 1.9T 1.3T 569G 70% /data vs. sudo du -h -d 0 /data 1.1T /data I tried using the btdu tool but I am not sure if I had it installed correctly as it didn't show the output like the examples shown on the github (https://github.com/CyberShadow/btdu)

btdu fastest and easiest tool to analyze space usage in compressed btrfs with lots of snapshots (especially in expert mode)

It doesn't seem BTRFS's fault. You could run btdu on your subvolumes to understand what's going on.

However, honestly, the best way to get a quick overview of where all your space is being used is btdu.

If you want to diagnose where you think there may be space used up that you don't quite understand, then btrfs fi du and third party tools btdu and compsize are useful.

And btdu to get an overall impressions of where space is being used if the above isn't useful enough.