xminer Posted May 31, 2013 Report Share Posted May 31, 2013 Anyone else seeing this error?Peers are Debian 32bit and Windows 7 32 bit, both version 1.0.134Receiving side error example(Windows 7):Error: 65daysofstatic-The Fall of Math-11-Aren't We All Running?.m4a - WriteToDisk: The filename, directory name, or volume label syntax is incorrect.Sending side error example (Debian 6):[20130431 10:02:25] Torrent 65daysofstatic-The Fall of Math-11-Aren't We All Running?.m4a status: 137 error: <NULL> meta: 1Other examples include "Alice In Chains - Dirt - Would?.m4a", etc, etc...Seems to only happen on directories or files with a "?" question mark in the name. BUT not all files or folder with question marks, some work fine. For example. Mega Death - Peace Sells... but who is buying?... stalled, would not transfer. But several others with "?" in the title seemingly worked fine, like "O Brother Where Art Thou?-..." did not fail.Renaming the folder and/or file, removing the "?" will cause the file to transfer as normal. Otherwise sync continually tries to transfer the file and gives no error, essentially stalling the sync until I intervened.Anyone else see this pattern? I wondering if the "?" issues is just a coincidence. Is there a formal bug tracker for Sync? Should be one... IMO.-xminer Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted May 31, 2013 Report Share Posted May 31, 2013 The "137 error: <NULL> meta: 1" message itself isn't anything to worry about - please see the unofficial FAQI wonder if the "?" issue is perhaps related to .SyncIgnore, as "?" is a "wildcard" character (as is "*"), so an actual physical "?" character may be tripping up BitTorrent Sync? ...have you made any modifications to your .SyncIgnore file, or are you using the default one that's created by BitTorrent Sync? Quote Link to comment Share on other sites More sharing options...
xminer Posted May 31, 2013 Author Report Share Posted May 31, 2013 I have not edited the .SyncIgnore file, so it is default. If the "137 error: <NULL> meta: 1" is not an error message then I do not see any indication in the sender side log indicating a problem, so perhaps that points the receiving side being the problem. I should also note that the "137 error" ALWAYS appears in context of the Receiving side error. I have not looked in the .SyncIgnore file. Is there a useful test we could do by removing or editing the .SyncIgnore file in attempt to rule out or prove that it may be acting like a wildcard in some broken way? Quote Link to comment Share on other sites More sharing options...
xminer Posted May 31, 2013 Author Report Share Posted May 31, 2013 Does Sync create .SyncIgnore automatically, I do not see them? Should they exist in the root folder on both peers? Quote Link to comment Share on other sites More sharing options...
xminer Posted May 31, 2013 Author Report Share Posted May 31, 2013 It appears to be transferring the files over and over, or more accurately, continuously, never finishing. This bug is pretty serious as if left alone will needlessly eat up bandwidth between the peers forever until the user notices. If you are doing a big transfer it could be days until you bother to look closely enough. Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted May 31, 2013 Report Share Posted May 31, 2013 Does Sync create .SyncIgnore automatically, I do not see them? Should they exist in the root folder on both peers?Yes, they are created automatically, but they are hidden by default (along with a ".SyncID" file and a ."SyncTrash" folder). All 3 are created within in each folder you're syncing, but if you don't see them, it'll be because your Windows OS is currently set to "hide" hidden/system files Quote Link to comment Share on other sites More sharing options...
xminer Posted May 31, 2013 Author Report Share Posted May 31, 2013 Indeed.Commenting out the default Ignore rules doesn't seem to have helped. I think it might be a more fundamental problem with punctuation handling on the receiving end. I have also seen it stall when a track has more than one set of ()'s or more than one set of ellipses - I wrote it of as random, as it doesn't seem to happen as often, but I also sure there are far far fewer instances of files that fit that pattern. Currently I have 3 songs stalling, two with ?'s and one with two sets of ()'s. This happened after transferring several dozen files with out a problem. I have not had it stall on anything that did not have fishy punctuation in the titles. But as these are song titles, its not unexpected or avoidable.I have transferred about 120 of 150GB successfully, had to edit files half dozen times and restarted a couple times so I have fairly reasonable sample size, over 20,000 files. I have successfully transferred over a hundred gigs of files with out any trouble, except for some of the files and dirs with ?, () and ellipses. Song's with these patterns are a fairly small percentage of the total, so outside of some other pattern I am not seeing it really looks like the right instance of punctuation is trouble some of the time.Note I am not a programmer, but I do write the occasional bash, perl or php script... I am aware that special attention is needed when parsing punctuation... so my thoughts go there, something is reading the names and it hitting the "?" and instead of seeing it as part of the string or name maybe it's being interpreted as code, or as an expression, maybe that's what its mentioning syntax...... but again, not a programmer... just a guess. Quote Link to comment Share on other sites More sharing options...
xminer Posted June 4, 2013 Author Report Share Posted June 4, 2013 The answer regarding the question marks now seems obvious. I didn't realize the Windows file system was still stuck in the 90's. question marks are not valid in Windows - Linux and OSX allow them. BUT...That still doesn't explain why files or directories with two sets of "..." or "()" wont transfer as those characters are perfectly valid in Windows, you can use them all day long as many times as you want. Better error handling would be good. The behavior when an invalid character is found should not be to continually attempt to transfer the files forever with out giving an error to the user. Skipping the file and logging the error and reporting it would be more optimal. Quote Link to comment Share on other sites More sharing options...
vadimt Posted June 6, 2013 Report Share Posted June 6, 2013 This bug with a "?" question mark in the names of files will be fixed in the next updates.Thanks! Quote Link to comment Share on other sites More sharing options...
highlander411 Posted June 19, 2013 Report Share Posted June 19, 2013 I'm also having this same issue. I can't help but wonder; if the wildcard is the issue why didn't it effect the transfer of the first 70GBs for me? Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted June 19, 2013 Report Share Posted June 19, 2013 I'm also having this same issue.Have you updated to the latest build? (1.1.15) Quote Link to comment Share on other sites More sharing options...
highlander411 Posted June 19, 2013 Report Share Posted June 19, 2013 No, I'm using 1.0.134 but it doesn't appear to be intuitive to install / uninstall this app in a windows environment. Quote Link to comment Share on other sites More sharing options...
eseelke Posted June 19, 2013 Report Share Posted June 19, 2013 No, I'm using 1.0.134 but it doesn't appear to be intuitive to install / uninstall this app in a windows environment.You can simply install the new version which will automatically upgrade the application. Due to the new version being drastically different, it will need to re-index all of your files. Quote Link to comment Share on other sites More sharing options...
highlander411 Posted June 19, 2013 Report Share Posted June 19, 2013 You can simply install the new version which will automatically upgrade the application. Due to the new version being drastically different, it will need to re-index all of your files.How is that achieved? I tried the basic download and run the installer and it just launches the previous app. I've also tried to click the button that says update but no change. Quote Link to comment Share on other sites More sharing options...
cosmos Posted October 15, 2013 Report Share Posted October 15, 2013 I broke my brain trying to understand why all is syncing well between Mac and Android OS phone except 2 my files with the name "2 - 1 - 1B.1 What is Democracy? [16 min]"!Now I got 2 successfully synced renamed by me files and 2 continuously syncing previous files with the question marks in the names.It was only 5 files in the folder, so I can easily find where the problem is. But if somebody has many files in a lot of subfolders and don't know exactly what the files there are, they'll get just the app for a quick battery discharge.It's good idea to notify user that some files cannot be synced because of forbidden symbols in the file names. It obviously applies to Linux based OS's. Mac v1.1.82Android v1.1.38 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.