For some subset of files (I have not figured out what determines this), the last file separator shows up as a backslash rather than a forward slash after comparing. This causes the Synchronize step to fail since the path becomes incorrect. Here is an example log entry:
Error Cannot copy file "/mnt/FLYANALYSIS_Documents/data/w_+;+_shits(5);R22D06_shitsR(5)/sinMir_VcontFreq_pro_lam30_60_90_C025_6TFs_180hz/2017/12_08\textStimData.csv" to "/home/labuser/SharedDocuments/data/w_+;+_shits(5);R22D06_shitsR(5)/sinMir_VcontFreq_pro_lam30_60_90_C025_6TFs_180hz/2017/12_08\textStimData.csv". Cannot read file attributes of "/mnt/FLYANALYSIS_Documents/data/w_+;+_shits(5);R22D06_shitsR(5)/sinMir_VcontFreq_pro_lam30_60_90_C025_6TFs_180hz/2017/12_08\textStimData.csv". Error Code 22: Invalid argument [lstat]
I tried deleting one of the folders at the destination and then re-synchronizing it back, but the same file had the same issue. This also only happens on my machine running Ubuntu 18.04, and not on another machine running Ubuntu 19.04.
Actually, now I see that yes, apparently this is caused by strange files that some computers show as having backslashes in their filename. You can probably ignore this issue.
