RomanZ

Hi sebknzl, Development is definitely aware of the issue. The main obstacle in resolving "My sync got stuck" issue is numerous different reasons that causing it. I would really appreciate if you can supply me with your logs full debug output from all your 3 machines when sync got stuck. In your case I would suspect either different characters case on Linux and Mac PCs - OR permissions issue. Thanks.

Hi unixunderground, There is no any centralised server which can force some keys \ folders, but I can advise to proceed with at least 2 solutions: 1. BTSync API. You can use API (which is actually HTTP-based) to control your peers and add folders simultaneously. 2. You can control your btsync with config file rather than with WebUI. And if you do so - you can make a script which connects one by one to all your peers and modifies config file to add new folders with new secrets.

Hi thesoul214, I'm a little bit confused with your setup. I guess that under "AP" you mean an Access Point which is running under BusyBox or some other Linux-based embedded, OS where you managed to install Linux version of BTSync. I do not understand what role USB plays in your setup as it is not a self-sufficient network node. Could you please elaborate? However, in general your concern is understandable. The more peers are "seeding" data, the faster "leeches" can receive it. This statement is more true for WAN networks as in WAN: a) asymmetric lines are very common Summary bandwidth between 2 peers is limited So, for WAN several peers can speed up BTSync download rate significantly as they load different channels. It is much less visible in local network as usually it has a wide bandwidth and it is symmetric.

Hi joelshannon, Indeed, currently behaviour on iOS and Android devices towards photo backup is different. We are going to fix it soon. For now I can advise you to set "sync_trash_ttl" advanced setting to "0", so all photos you delete on Android device will be moved to .SyncArchive but will never be deleted from there. Currently Android Photo backup is technically a read-only sync folder.

FDW, You can try to do it from UI or from console. In UI: - Run activity monitor, see which user owns Bittorrent Sync. - Find the folder which failed to write into. - Right-click on the file, "Get Info", see "Sharing & Permissions" - Make sure that your user is allowed to both read and write, and this is the same user which runs BTSync For console you need to: "ps aux | grep Bittorrent" to find the process and the owning user. "cd <location>" to get to problematic folder "ls -l" to see permissions and user who owns the folder. Again, you need to have RW permissions for your user and make sure that the user is same as running BTSync "chown <user_name> <folder_name>" to adjust owner "chmod 777 <folder_name>" to adjust permissions to be as permissive as it is possible

Hi all, The issue "Sync not completing / get stuck" is known and very hard to debug due to numerous origins. We are working very hard to eliminate all of them or make common mistakes (like permissions, locked files, etc.) identifiable by users. If you experience such issue - debug logs are highly appreciated, including all peers. @casacota, The file .syncold usually contains the backup of the file when file gets transferred to your peer partially from another location. After the transfer is successful, .syncold gets moved to .SyncArchive folder (if allowed in settings). The file .synctemp usually contains the backup of the file when file gets transferred completely. When transfer complete, original file is moved to .SyncArchive and .synctemp is renamed to a new file. In normal behaviour these files shouldn't stay longer than transfer goes. If you suddenly realize that these files stay for a long time and when Sync finished syncing - it is abnormal and I'll highly appreciate logs (full debug, of course) for such case. If they stay longer - they can prevent syncing for the files with the same name.

I would advise to turn logs off meanwhile. Keeping debug logging on is going to consume disk space extensively.

Hi CrazyChoco, Read-only peer can't deliver changes to other peers. BTSync needs to sign changes using read-write secret.

Hi all, As @disconnect mentioned, "move" logic is implemented in BTSync, however, it is not ideal yet and can be improved. If anyone has a stably reproduced use case when btsync prefers re-uploading instead of moving - I appreciate assistance, in form of: 1. Detailed description of replication (including OS, size and amount of files, LAN\WAN, bandwidth, etc.) 2. Debug logs from reproduction.

Hi Junge, Android is a fully supported platform, which means - if you delete the file from Android device, and it has read-write key - your file is going to be deleted from other peers as well. If you want to see whole directory, sync files on demand and remove them from android device once you no longer need them without affecting any other peers, I'd recommend you next settings: 1. Share read-only secret to your android 2. Disable auto-sync. When you need a file - tap it to sync it. When you don't need it anymore - delete it, your file removal won't affect other peers as you have read-only key. Unfortunately, "un-sync" option you are looking for is not available now immediately, so you have to use described workaround.

Hi nmccloud, It is normal behaviour that folders get created. If you want to avoid it, try putting it in "AppData\Local\Microsoft\Windows\Temporary Internet Files" format, i.e. avoiding trailing backslash and asterisk.

Hi deoren, Recently I've found another reason which might cause sync process to stuck. If you have the same file on different peers written differently (lower\upper case of symbols), sync might get stuck. Also note, that when your logged in after reboot, there will be plenty of processes running under your user account - having dozens of handles opened to your user profile folder. So, reboot is not a panacea to make sure that your sync folder has no open files. The precise reason could be found by collecting debug logs, from all peers. If you do so - please provide logs to me so I can analyse what's happening inside. Also, there was a nice script done by one of community members (yottabit) which allows to sync user profile in a smart way avoiding temp files, caches, and other stuff, useless to be backed up.

deoren, Sorry for ambiguity. "folder_rescan_interval" parameter has no relationship to current discussion. Just noted, that zero is a valid value both for sync_trash_ttl and folder_rescan_interval and leads to disable them completely. For this topic only sync_trash_ttl is relevant. [Aside the main discussion, if you put folder_rescan_interval to "0" it won't disable new items from showing up, as btsync gets a notifications from OS about changes in the folders. However, in some OSes theses notifications are not reliable enough]

Hi, It is design. Backup assumes - backing up all your photos, also for the case if they are deleted accidentally.

Hi jwinter, AzimutTheUt, I'll need debug logs to identify what is the root cause of non-syncing. jwinter - you need to put the "debug.txt" file to the folder where btsync binary stays, then you'll get an extended logging. Please see details here. After I get the logs - I can tell you what get stuck (and report to developers for improving app). Thanks.

Hi who281, You can sync data between true crypt volumes, but there are couple of peculiarities about it: 1. If you are syncing files inside TrueCrypt volume: - TrueCrypt not always notifies OS about the file changes. Which means that sometimes file change is missed, and will be synced only during full rescan (once per 10 minutes by default, can be adjusted) - TrueCrypt volume needs to be mounted to do actual sync - Files on true crypt volume will be accessible in OS when it is mounted (I mean - TrueCrypt adds security value because unauthorised person can't access it when it is unmounted, but when it is mounted - it is pretty much the same as any other drive) 2. If you are syncing the volume file itself - It is going to be big. And when it changes, BTSync has to re-hash whole file to find the differences. It is going to load your CPU a lot. - Different programs behave differently with their documents. In case of TrueCrypt it does not change modification time for the volume file for security reasons, so it is impossible for BTSync to determine which volume to sync, and which to overwrite. So, due to #2 - I would avoid syncing TrueCrypt volume files. As for the cross-platform file syncing - it is allowed, please consider next peculiarities: 1. On different platforms different symbols are considered to be valid or invalid in filenames (for example, "*" is a valid symbol for Mac, but is prohibited for FAT/NTFS file systems) 2. Different OSes stand differently towards case sensitivity of file names. 3. Different OSes has different permission patterns, so be sure that btsync has enough permissions to write data in Sync'ed folders.

abc123, There might be another reason for getting stuck for the sync. Didn't you rename the files by changing only the case, or - is there a chance that the same files on different peers might have a filename in different case? It can stop the sync as well. It is a known issue which will be fixed in new release, but still present in 1.2.82

Hi stangz989, Thanks for the feature request. We'll consider it for future releases.

Hi zigz14, Few items to check : 1. Check if you are in the same folder as btsync binary 2. Check if you btsync binary have enough permissions to be executed by your current user

Hi bmchristian, A few questions to clarify your setup. 1. Do I understand correctly that all 3 devices share the same secret? 2. When iPhone does not see any devices connected - is it in the same LAN? If no - how is it connected to internet? If over 3G - it your traffic might be blocked by your provider. 3. Can you please clarify about your Mac? You say that you entered a secret, but never added a folder? 4. The "Sync stopped" status might be result of non-synchronised time or wrong time zone on one of your devices, I suggest checking it.

jwilker, Could you please check that user, which runs btsync has enough permissions to write into that folder? It might happen that btsync runs as a different user, which has no enough permissions. When folder added, BTSync adds some service information inside immediately, so lack of permissions is a result of this error popup.

crazyk4952,, Few comments while we are working on reproduction. 1. BTSync version you mentioned is 1.2.2.2, while latest available is 1.2.82 (and it has a bunch of speed optimization). Could you please upgrade and see if issue persists? 2. There is another good test I'd like to ask you to do. Could you please try to sync with all the same parameters a folder with files 1..2Mbytes each, amount of files should be enough to make a graph. In this case BTSync is going to maintain different amount of simultaneous connections. Thank you for your help.

nickluck, You have a different issue. In your case BTSync wants to sync some data, but can't do it by some reason. Usually it happens when some files / folders can't be read (locked by another app, wrong permissions). Can you please provide a log so I can take a look what get stuck?

Sorry for inconvenience. We have a very limited resources assigned to support now, however this is going to improve in closest couple of months.

crazyk4952, Thanks a lot for the info. I'll update as soon as we have some news on saw-formed BTSync traffic issue.