Mover comes running along, and dutifully moves the file(s) that aren't actually in use to the array, but then the app goes and decides to recreate the file on the cache drive.
You have to work with disk shares (or reference a disk share directly in say an app template - /mnt/cache/appdata) )ĮG: Easiest way I can think of for one to be created is to have appdata share as use cache: yes, and apps set to /mnt/cache/appdata. I have seen how because only few are affected that it's not a "thing" but this is still a problemĭuplicates are pretty hard to create under normal circumstances. So as I said before this is multi user problem, can there be some sort of looking into how to troubleshoot this please. I'll work on finding out the cause, but I thought I would post this workaround to fixing the problem without having to manually go through everything. The program suffers from stack overflow errors if you try to compare too many files, but once I figured out the sweet spot, it's been easy to search and find these thousands of dups. I found the app Czkawka - and this allowed me to do a binary compare and then delete the duplicates. In any case, I needed a way to find and delete these duplicates. I do a lot with Musicbrainz Picard - and a lot of the dups were flac files, so maybe that's an issue?
I never work at the disk level - only the share level, so I do not know how this happened. I know this reply is 3.5 years later, but I was searching for a solution to this problem.ĬA Fix Common Problems found hundreds of duplicate files on two of my disks. If you continue to have problems with duplicate files being created, you need to make SURE that none of your file creation or management tools reference /mnt/diskX or /mnt/cache, only /mnt/user paths when creating or moving your data. If you then "clean up duplicates" and delete the file on disk1, then your changes will be lost, and the file that shows up in /mnt/user/folder/document.txt will be the original, not the modified copy.īottom line, you should probably use a clean up method that employs full binary comparison to determine duplication, not just file name collisions. They will be reported as duplicate file names, but the contents are different. If you access the file /mnt/user/folder/document.txt, it only modifies the document on the first disk, so the 2 documents are NO LONGER DUPLICATES.
when a copy has been made to a different disk with the same path, those files are binary duplicates, but ONLY if no changes are made to the files. You are stating that the files are duplicates, and if that is the case, then the solution is to delete one of the copies. Keep in mind the semantics here can be important.
0 kommentar(er)
