Robocopy sees differences in files even when there are none BUG
Edit: Is this taken seriously, or did I post it at the wrong place? I hope I did not waste my time trying to report a bug in a widely used tool. Files have same time to the second and same content to the byte, the only thing is that source is a network drive. Does Microsoft not intend to fully support network drive as source? Edit 2: I dropped robocopy completely and found a quite good alternative: https://freefilesync.org/. After a small donation, it even supports multithreaded copying. Not a command line tool unfortunately, but at least it is able to know when files are similar and it doesn't copy them again each time. When I copy files from my network drive to a local folder and immediately re-run the command, all files are copied again instead of being skipped like they're supposed to. robocopy "\\network\Document\Migration" D:\Migration /S /FFT Please see my superuser question for more infos https://superuser.com/questions/1733527/robocopy-from-network-drive-doesnt-skip-duplicates. I searched elsewhere on the web and found that some german person in 2013 had the exact same problem - no issue was found https://www.synology-forum.de/threads/robocopy-sieht-identische-dateien-als-geaendert-an-fft-hilft-nicht.41341/ I don't know if this is linked to https://social.technet.microsoft.com/Forums/en-US/6eba1f81-8666-42ce-9aaa-e9cf8814c64f/robocopy-problem-under-windows-8 I am flabbergasted that robocopy cannot be trusted to do this so basic thing which is comparing 3 things: name, date and size. More so that the switch that was created for this purpose /FFT does not work for me. Is there a way to see WHAT differences robocopy sees between the files? Because according to robocopy "\\network\Document\Migration" d:\migration /l /ts /nc /ndl /njh /njs /FFT All files are similar (same date) and `fc` shows that there are no differences. 0 2022/07/25 11:31:55 d:\migration\file 1.txt 0 2022/07/25 11:32:06 d:\migration\file 2.txt 0 2022/07/25 11:32:18 d:\migration\File 3.docx 0 2022/07/25 11:31:55 \\network\Document\Migration\file 1.txt 0 2022/07/25 11:32:06 \\network\Document\Migration\file 2.txt 0 2022/07/25 11:32:18 \\network\Document\Migration\File 3.docx (If you pay close attention, this result from the command above in and itself is wrong, as I didn't include the "/IS" switch that enables same files. Same files should not be displayed at all)
Robocopy - Bugs and suggestions
Hello, I don't really know where to reach out, but I really do love Robocopy and hope that someone inside MS finds the tool valuable enough to continue it's development. I've come across a few issues as of late: If setting it up to monitor a source using /MOT:n, to make it check for changes every n minutes, it fails to detect changes made if there is a copy operation in progress. Also reported here: https://superuser.com/questions/1040996/robocopy-not-seeing-new-files-if-in-the-middle-of-copying-a-file Using the /NP switch breaks the functionality of the /IPG switch and transfers run at maximum speed It would be nice if the logging functionality could release the file handle between writes so that log rollover could be handled externally, for situations when robocopy is used for always-on monitoring applications Best regards Alexander
