Closed felciano closed 1 year ago
This is not a bug. Works as designed. Fclones reports always both sides of the duplicate match, because it has no idea which of the duplicates you want to remove. If multiple files are present under one isolated roots, they are counted as one, but still all are reported.
@pkolaczk this makes sense -- thanks for the clarification.
In the isolate
scenario, is there a way to tell which of the duplicates in the first directory will be used if you elect the link
option?
That is, under the above scenario, if I tell fclones
that I want to replace duplicates with links, will file .../dir-2/A.JPG
end up being linked to .../dir-1/A.JPG
or .../dir-1/A copy.JPG
?
According to the README docs,
--isolate
finds files that match across two directory trees, without matching identical files within each tree. However this doesn't seem to be the case. Consider this file structure, where all the files are identical:Then run the following:
I would expect this to find duplicates of files in
dir-1
indir-2
only, and vice versa. Instead I get:The first two entries in this report indicate that
A.JPG
andA copy.JPG
are duplicates, which is true, but should be excluded with the--isolate
flag.