denao Posted December 12, 2013 Report Share Posted December 12, 2013 Is anybody else getting this issue when using encrypted secrets? (as first posted by @mothlike in the Developers forum at http://forum.bittorrent.com/topic/25107-weird-error-when-sync-to-the-encrypted-peer/) [20131122 08:48:06.410] LoadTorrent: file /var/BTSync/Динамика/2TD4GHMZFXNG6IYXZVYZJSF5ZSLHHKYSY2EGMLA/D2LSYBAAWXVWRDZZQJ5MHPWZJ7JF2UOOTAXAP2DX4IFIUIPJW5HQ/4MWWEAZRA7WNFWIMPFJ5M37YLQ7KX3BZHZDPYQYO4JK3O2USQO4QQXTSUC5QZ55XLDCD2PF7BP4XVZ4SZ3S24HFBNRJGS22YZVQGJQYNKJP33BH2ZMQ55HU63NQL6ZV4U34NSNV77LNP4ZXMRF3I3LROHPJ46HHC5556QJKG5JNIU34S3XQXKQRVRD55RU74MNK5NIA7MGQJOSAD4K22UOFEBKU2ROE7SAVXR3BIIMDGFRYYDQRIBJP5I3XI3U6HXRBNQILI6OINOXZB5XNLUZALM3DT2IRI7DCQTQPEONMRWJU4AY2A exists, but failed to get mtime 36[20131122 08:48:06.411] LoadTorrent: file /var/BTSync/Динамика/2TD4GHMZFXNG6IYXZVYZJSF5ZSLHHKYSY2EGMLA/D2LSYBAAWXVWRDZZQJ5MHPWZJ7JF2UOOTAXAP2DX4IFIUIPJW5HQ/4MWWEAZRA7WNFWIMPFJ5M37YLQ7KX3BZHZDPYQYO4JK3O2USQO4QQXTSUC5QZ55XLDCD2PF7BP4XVZ4SZ3S24HFBNRJGS22YZVQGJQYNKJP33BH2ZMQ55HU63NQL6ZV4U34NSNV77LNP4ZXMRF3I3LROHPJ46HHC5556QJKG5JNIU34S3XQXKQRVRD55RU74MNK5NIA7MGQJOSAD4K22UOFEBKU2ROE7SAVXR3ET45Q5O6AWCPQYXTI464JR4VQPGR4QDGMZVL3HLBFW5EED7YAJIPWHY3IHVNFWF2AH6DJ6TF4HMS35N5UMC4NEI3XUW4SLO7JT73WDW exists, but failed to get mtime 36 Im seeing exact same error. Using version 1.2.82. Any ideas? Quote Link to comment Share on other sites More sharing options...
vadimt Posted December 13, 2013 Report Share Posted December 13, 2013 Path to your file is too long and it doesn't match your OS conditions. Please change it.Thanks! Quote Link to comment Share on other sites More sharing options...
denao Posted December 13, 2013 Author Report Share Posted December 13, 2013 How would I know what path/file is that? It is encrypted! Is there any log in the non-encrypted peer that can help me to locate this file? Thanks! Quote Link to comment Share on other sites More sharing options...
vadimt Posted December 13, 2013 Report Share Posted December 13, 2013 How would I know what path/file is that? It is encrypted! Is there any log in the non-encrypted peer that can help me to locate this file? Thanks! var/BTSync/Динамика/2TD4GHMZFXNG6IYXZVYZJSF5ZSLHHKYSY2EGMLA/D2LSYBAAWXVWRDZZQJ5MHPWZJ7JF2UOOTAXAP2DX4IFIUIPJW5HQ/4MWWEAZRA7WNFWIMPFJ5M37YLQ7KX3BZHZDPYQYO4JK3O2USQO4QQXTSUC5QZ55XLDCD2PF7BP4XVZ4SZ3S24HFBNRJGS22YZVQGJQYNKJP33BH2ZMQ55HU63NQL6ZV4U34NSNV77LNP4ZXMRF3I3LROHPJ46HHC5556QJKG5JNIU34S3XQXKQRVRD55RU74MNK5NIA7MGQJOSAD4K22UOFEBKU2ROE7SAVXR3ET45Q5O6AWCPQYXTI464JR4VQPGR4QDGMZVL3HLBFW5EED7YAJIPWHY3IHVNFWF2AH6DJ6TF4HMS35N5UMC4NEI3XUW4SLO7JT73WDW - it's more than 255 bytes. You can check log file on non encrypted node:Windows: %APPDATA%\BitTorrent Sync\sync.log Mac: ~/Library/Application\ Support/BitTorrent\ Sync/sync.log Linux: ./sync/sync.log Thanks! Quote Link to comment Share on other sites More sharing options...
denao Posted December 15, 2013 Author Report Share Posted December 15, 2013 it's more than 255 bytes. You can check log file on non encrypted node:Windows: %APPDATA%\BitTorrent Sync\sync.log Mac: ~/Library/Application\ Support/BitTorrent\ Sync/sync.log Linux: ./sync/sync.log Thanks! Bingo! I just renamed the files with longest path and voila... syncing again. Thanks a lot, man! BTW, I didnt find a single line about this situation on logs from non-encrypted peers... very annoying. Quote Link to comment Share on other sites More sharing options...
scrod Posted March 6, 2014 Report Share Posted March 6, 2014 (edited) I'm also experiencing this error when attempting to use an encrypted "backup" secret. The client is running on HFS+ (Mac OS X) and is attempting to create 256 character file names, which exceeds the limit for file names. None of the files are syncing to the encrypted peer -- just a bunch of empty folders. As I can't control what BitTorrent Sync chooses to name its encrypted files, I don't see how I can prevent this from happening. Edit: both clients are running version 1.2.91. Edited March 6, 2014 by scrod Quote Link to comment Share on other sites More sharing options...
cpbotha Posted March 22, 2014 Report Share Posted March 22, 2014 I've run into this same problem when syncing with an eCryptFS filesystem. It turns out that that has a filename limit of 143 characters, so now I'm seeing: [20140322 08:26:30.659] LoadTorrent: file /volume1/btsync-cpbotha/work/code/xxxxxxxx/yyyy/htmlcov/_home_cpbotha__virtualenvs_yyyy_lib_python2_7_site-packages_easy_thumbnails_migrations_0015_auto__del_unique_thumbnail_name_storage_hash__add_unique_thumbnail_sou.html exists, but failed to get mtime 36 This is a design limit of eCryptFS: https://bugs.launchpad.net/ecryptfs/+bug/344878 I'll have to figure out some other way of encrypting the btsync trees on my synology. Any tips? (eCryptFS is what happens when you create an encrypted share) Quote Link to comment Share on other sites More sharing options...
himselfv Posted April 4, 2014 Report Share Posted April 4, 2014 I'm also having this problem. The problem is only in the length of a single filename which makes it a bit easier (full path can be of any length). But some solution would be great. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted April 4, 2014 Report Share Posted April 4, 2014 Himselfv, Are you getting the single filename longer than allowed by your OS \ FS? Could you please share which OS and filesystem do you use? Quote Link to comment Share on other sites More sharing options...
himselfv Posted April 5, 2014 Report Share Posted April 5, 2014 RomanZ, Windows 7 SP1/NTFS as a client, CentOS/xfs as an encrypted server. I've tried:share\some folder\some folder\some folder\some folder\some folder\some folder\some folder\some folder\some folder\some folder\some folder\some folder\some folder\some folder\file.txt -- works with BTSync share\some folder\very long filename longer than 143 characters or whatever the limit is but shorter than 255 chars.txt -- stuck in "Updating" like with other people in this thread Quote Link to comment Share on other sites More sharing options...
RomanZ Posted April 7, 2014 Report Share Posted April 7, 2014 Himselfv, There is certain limit of filename on windows (260 symbols). File encryption makes encrypted file name longer, so for now I would advise avoiding filenames longer than 120 symbols if your encrypted node is windows. Roman. 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.