This is sort of a follow-up to this question.
If there are multiple blobs with the same contents, they are only stored once in the git repository because their SHA-1\'s
The scripting answers from your linked question pretty much apply here too.
Try the following git command from the root of your git repository.
git ls-tree -r HEAD
This generates a recursive list of all 'blobs' in the current HEAD, including their path and their sha1 id.
git doesn't maintain back links from a blob to tree so it would be a scripting task (perl, python?) to parse a git ls-tree -r output and create a summary report of all sha1s that appear more than once in the list.