btdu VS jdupes

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.

I recommend the use of jdupes, a fork of the well-known fdupes, to find duplicate files.

200 lines of Nim [1] seems to run about 9X faster than the 8000 lines of C in fdupes on a little test dir I have. If you need C, I think jdupes [2] is faster as @TacticalCoder points out a couple of times here. In my testing, `dups` is usually faster than `jdupes`, though.

[1] https://github.com/c-blake/bu/blob/main/dups.nim

[2] https://github.com/jbruchon/jdupes

There's always the well-respected tool, Czkawka. Or, of the CLI is your thing, jdupes is a good option.

My research into this many years ago turned out that jdupes was the right / best solution I could find for my usecase.

https://github.com/jbruchon/jdupes

Though that works fine from a script perspective I'd like some more interactive way of sorting directories etc. Identifying is just the first step, jdupes helps with linking the files (both soft and hard links comes with caveats though!) but that is mostly to save space, not to help in reorganisation.

I can work it out by looking at https://github.com/jbruchon/jdupes.

I have looked at a few alternatives and think jdupes is the one for me. Then I found out it was not multi-threaded so will give it a go but the developer of jdupes recomended fclones (https://github.com/jbruchon/jdupes/issues/186) if you were dealing with large file systems and wanted multi-threading. But as I am using a HD it may not be necessary.

jdupes is a fork of the old standby fdupes, but it has a Win32 release as well as supporting POSIX.

jdupes is a tuned fork of the well-known fdupes, and has Win32 releases.