13 comments

[ 0.20 ms ] story [ 47.0 ms ] thread
I personally found fdupes to be slower and more limited than dupfiles [0].

I switched to dupfiles about a year ago and haven't had any problems yet.

[0]: http://liw.fi/dupfiles/

I used this when I was working on a product that used automated tests to upload files repeatedly during the day. The volume of test files was so great that it continually put pressure on the storage -- more pressure than the uploads from the actual users.

Fortunately the uploads were from a set of a few dozen static files, and de-duplicating the data via fdupes was able to drop disk usage by a factor of 20-50x.

Is this multiplatform? I think it's interesting how many projects forget to mention what operating system they target.
It's worked on every linux/unix variant I've tried it on (including OS X where it's in homebrew), but I can't swear to anything non-*nix.
I did something similar to this a while back, called qdupe[0], written in Python. It doesn't do the deleting for you, but is very fast at identifying duplicates if you have a lot to compare. Based on the fastdup algorithm.

[0] https://github.com/cwilper/qdupe

It's not exactly clear, but I'm assuming this is some kind of automated hard-linking utility? Or does it use its own special magic? (filesystem type restrictions?)
(comment deleted)
It just finds (and optionally deletes) duplicate files. For hardlinking the duplicates, there's freedup.