Today I encountered a problem where the Mac client (1.3.109) gets stuck or crashes when attempting to sync files that contain certain non-ASCII characters from a Linux (ARM) host. From the debug log, it seems that the client, after downloading the last block, tries to commit the file to the Mac's file system, and then the file system rejects the file name, leaving the process stuck. After renaming the file on the Linux host and restarting the Mac client, the client happily syncs the file (and in my case, gets stuck on the next file...). I see the following relevant messages in the debug log: The Mac console shows the following right after this happens: Please fix the Mac client so that it does not try to save files with characters not allowed by OS X. For me it would be okay if Sync removes the characters from the file name (or encodes them using urlencoding, for instance). By the way, I've been syncing folders with these files for over a year now between two ARM boxes, without issue... A related issue is that the file system on the ARM Linux boxes is case-sensitive, whereas my Mac's file system is not. So if the ARM box has two files "A.txt" and "a.txt", syncing gets stuck on the Mac end as well..
