binarybrian Posted September 19, 2014 Report Share Posted September 19, 2014 In bittorrent sync version 1.4.75 and 1.4.83 any file names containing Korean characters will not sync. The log files on both machines indicate that the files are skipped due to an "invalid UTF8 file name". This problem did not exist with version 1.3.109. The problem seems to be unique to Korean characters. I've tried both Chinese and Japanese and files with these characters synchronize properly. System Information:Gentoo LinuxKernel Version 3.14.14File System: ext4 cat sync.log |grep -i versionversion: 1.4.83 The relevant section of the sync.log file is shown below.[20140918 22:35:30.401] SF[9811]: UpdatePeersStat[20140918 22:35:30.401] SF[9811] [6F79]: up:0 down:0[20140918 22:35:30.401] ScheduledTask:UpdatePeersStat invoked:timer reason:FinishStateSync[20140918 22:35:35.989] SyncFolderNotify: "감사합니다.txt", event = "IN_CREATE"[20140918 22:35:35.989] [OnNotifyFileChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:35.989] SyncFolderNotify: "감사합니다.txt", event = "IN_ATTRIB"[20140918 22:35:35.989] [OnNotifyAttrChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:35.989] [OnNotifyFileChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:35.989] SyncFolderNotify: "감사합니다.txt", event = "IN_CLOSE_WRITE"[20140918 22:35:35.989] [OnNotifyFileChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:36.647] SyncFolderScanner: Processing watch item "/mnt/teragon/K-Sync/test/감사합니다.txt", now = 1411101336, time = 0[20140918 22:35:36.648] SyncFolderScanner: Posting update event for file "/mnt/teragon/K-Sync/test/감사합니다.txt"[20140918 22:35:36.648] SyncFolderScanner: Skiping file '/mnt/teragon/K-Sync/test/감사합니다.txt' with invalid UTF8 file name[20140918 22:35:36.648] FC[9811]: attr changed - rocessing folder /mnt/teragon/K-Sync/test/감사합니다.txt 1411101335[20140918 22:35:36.648] [OnNotifyFileChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:37.648] SyncFolderScanner: Processing watch item "/mnt/teragon/K-Sync/test/감사합니다.txt", now = 1411101337, time = 1411101327[20140918 22:35:37.648] SyncFolderScanner: Posting update event for file "/mnt/teragon/K-Sync/test/감사합니다.txt"[20140918 22:35:37.648] SyncFolderScanner: Skiping file '/mnt/teragon/K-Sync/test/감사합니다.txt' with invalid UTF8 file name[20140918 22:35:42.146] SyncFolderNotify: "감사합니다.txt", event = "IN_CLOSE_WRITE"[20140918 22:35:42.146] [OnNotifyFileChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:42.648] SyncFolderScanner: Processing watch item "/mnt/teragon/K-Sync/test/감사합니다.txt", now = 1411101342, time = 1411101333[20140918 22:35:42.649] FC[9811]: file changed - processing file "/mnt/teragon/K-Sync/test/감사합니다.txt"[20140918 22:35:43.649] SyncFolderScanner: Processing watch item "/mnt/teragon/K-Sync/test/감사합니다.txt", now = 1411101343, time = 1411101333[20140918 22:35:43.649] SyncFolderScanner: Posting update event for file "/mnt/teragon/K-Sync/test/감사합니다.txt"[20140918 22:35:43.649] SyncFolderScanner: Skiping file '/mnt/teragon/K-Sync/test/감사합니다.txt' with invalid UTF8 file name[20140918 22:35:48.024] SyncFolderNotify: "감사합니다.txt", event = "IN_MODIFY"[20140918 22:35:48.024] [OnNotifyFileChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:48.024] SyncFolderNotify: "감사합니다.txt", event = "IN_MODIFY"[20140918 22:35:48.024] [OnNotifyFileChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:48.024] SyncFolderNotify: "감사합니다.txt", event = "IN_CLOSE_WRITE"[20140918 22:35:48.024] [OnNotifyFileChange] "/mnt/teragon/K-Sync/test/감사합니다.txt", source = "NULL"[20140918 22:35:48.649] SyncFolderScanner: Processing watch item "/mnt/teragon/K-Sync/test/감사합니다.txt", now = 1411101347, time = 1411101341[20140918 22:35:48.650] FC[9811]: file changed - processing file "/mnt/teragon/K-Sync/test/감사합니다.txt"[20140918 22:35:49.650] SyncFolderScanner: Processing watch item "/mnt/teragon/K-Sync/test/감사합니다.txt", now = 1411101348, time = 1411101341[20140918 22:35:50.650] SyncFolderScanner: Processing watch item "/mnt/teragon/K-Sync/test/감사합니다.txt", now = 1411101349, time = 1411101341[20140918 22:35:51.650] SyncFolderScanner: Processing watch item "/mnt/teragon/K-Sync/test/감사합니다.txt", now = 1411101351, time = 1411101341[20140918 22:35:51.650] SyncFolderScanner: Posting update event for file "/mnt/teragon/K-Sync/test/감사합니다.txt"[20140918 22:35:51.650] SyncFolderScanner: Skiping file '/mnt/teragon/K-Sync/test/감사합니다.txt' with invalid UTF8 file nameSteps to reproduce:1. From the web UI on two different machines choose a folder to synchronize.2. Go https://translate.google.com/?hl=en#en/ko/Thank%20You to generate some Korean characters. 3. Open a terminal and cd to the shared folder on Linux machine Alice. 4. Type "touch 감사합니다.txt"5. Type "touch hello.txt"6. Wait 5 minutes and observe on Linux machine Bob that the 'hello.txt' file has arrived but that the file with Korean characters has not been received.7. Open the sync.log on Alice and look for the line "Skiping file '감사합니다.txt' with invalid UTF8 file name".8. Bonus observation: 'Skiping' is spelled wrong in the log file. Expected result: Files with Korean characters are not skipped. Quote Link to comment Share on other sites More sharing options...
metalkih Posted September 24, 2014 Report Share Posted September 24, 2014 exactly same issue in OS X Bittorrent Sync 1.4.83.So I downgraded 1.3.x Quote Link to comment Share on other sites More sharing options...
RomanZ Posted September 24, 2014 Report Share Posted September 24, 2014 Hi all, Could you please run a command in console and send me and output?ls | iconv --from utf8I suspect that you might have incorrectly encoded filenames in your foler. Please send output to syncapp@bittorrent.com and refer this topic and my name in message subject. Thanks! Quote Link to comment Share on other sites More sharing options...
agitato816 Posted September 30, 2014 Report Share Posted September 30, 2014 Hi, I have exactly same problem on Ubuntu 14.04 BTSync Version 1.4.83 (1.4.83) On Mac OSX and Windows no issue with Korean(Hangul), but it only occurs on Ubuntu Korean filename and foldername. Please fix it for korean Linux Users! I'm very annoying with it. I don't understand that there is no problem with Japanese and Chinese, but only Korean.akntk@umi:~/.btsync$ akntk@umi:~/.btsync$ cat sync.log |grep -i versionversion: 1.4.83[20141001 04:29:03.672] Loading config file version 1.4.83akntk@umi:~/.btsync$ ls | iconv --from utf818D4AD97B00AD6FEE292B8474E45DD3D7B3191E1.db18D4AD97B00AD6FEE292B8474E45DD3D7B3191E1.db-shm18D4AD97B00AD6FEE292B8474E45DD3D7B3191E1.db-walbtsync-gui.loghistory.dathistory.dat.oldsettings.datsettings.dat.oldsync.datsync.dat.oldsync.lngsync.logsync.log.bakwebui.zipakntk@umi:~/.btsync$ uname -aLinux umi 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Quote Link to comment Share on other sites More sharing options...
RomanZ Posted October 1, 2014 Report Share Posted October 1, 2014 @agitato816We've managed to find the root cause and fix it. Please expect fix in next release build. Quote Link to comment Share on other sites More sharing options...
agitato816 Posted October 3, 2014 Report Share Posted October 3, 2014 @RomanZ Thanks for the confirm. I downgraded to 1.3.109 all of my machine include Mac Linux Windows. The older version has no problem yet.@RomanZFYI, with ver 1.4.83 the Korean issue is not only in Linux, but also Windows and Mac. Thanks for your time and effort. Quote Link to comment Share on other sites More sharing options...
binarybrian Posted October 9, 2014 Author Report Share Posted October 9, 2014 Yes, thank you RomanZ for looking into this and to agitato816 and metalkih for bumping with additional info so it could get some attention. Looking forward to the update. Quote Link to comment Share on other sites More sharing options...
Kerenon Posted October 16, 2014 Report Share Posted October 16, 2014 After upgrading to 1.4.91 on my x64 Ubuntu Linux box, I get the same error messages, and none of my files containing Hungarian UTF-8 characters is synced to other devices/computers. Reverting to 1.4.82 fixes the problem. Quote Link to comment Share on other sites More sharing options...
gorf Posted October 28, 2014 Report Share Posted October 28, 2014 Chinese is the same information.1.4.91 and 1.4.93 are all have this bug. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted October 29, 2014 Report Share Posted October 29, 2014 @allThis is known issue. It affects all files with non-ASCII characters in the filename, Linux computers only. Please expect fix in next build (sorry - no ETA). Quote Link to comment Share on other sites More sharing options...
levabd Posted October 30, 2014 Report Share Posted October 30, 2014 (edited) Same problem with Cyrillic. version 1.4.93 Will wait the next version. Edited October 30, 2014 by levabd Quote Link to comment Share on other sites More sharing options...
Bomfunk Posted October 30, 2014 Report Share Posted October 30, 2014 Confirmed the same problem with Cyrillic:[20141030 14:21:52.291] SyncFolderScanner: Skiping file '/home/bomfunk/Docs/bomsync/русский тест.txt' with invalid UTF8 file nameUsing only Linux x64 systems to sync files with Russian names. The version is the latest available - 1.4.93.I didn't experience this problem before the few latest updates, the application seemed to be pretty reliable. Hoping that the fix will come soon. Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted October 30, 2014 Report Share Posted October 30, 2014 @allAs has now been mentioned numerous times; This is a known issue affecting files with non-ASCII characters in their filenames on Linux computers only. As RomanZ indicated just yesterday, "Please expect fix in next build (sorry - no ETA)" Quote Link to comment Share on other sites More sharing options...
Bomfunk Posted October 31, 2014 Report Share Posted October 31, 2014 Thank you - I've seen the message, thus stated "Hoping that the fix will come soon."Sorry for sharing my observations in addition to what has been posted above. Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted October 31, 2014 Report Share Posted October 31, 2014 @all, this issue should now be fixed in 1.4.99 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.