jbruchon
commented
1 year ago This happens if you specify paths twice, either explicitly or implicitly via a parent or symlink. In the jdupes fork I wrote a double-traversal prevention routine that stops this from happening, but it uses extra memory and processing time and right now I'm having to completely rewrite the code due to poor scaling. It also causes problems with some network shares and cloud storage such as Google Drive. Your best bet for now is to figure out why the same parent directory is getting into the program twice and change your invocation so it doesn't happen. This problem is not unsolvable in code but it's also far from a simple fix. Better to prevent it from happening at invocation than relying on a safeguard to protect you from yourself. 😉
AgneTallroth
fdupes: Version : 1:2.2.1-2 Platform: Aritix Linux 5.15.82-1-lts
According to the following output, I might have delete one of each, leaving me with nothing left, since when I do a simple ls in this directory, there is only one of each.