wabackpacker

[Solved] Syncing Not Completing

Recommended Posts

First, I want to express my gratitude and thanks for building this amazing tool! Side note, before I get into my challenges... I own a data center company in Seattle and if we can donate any server/data center resources towards the project I'd be happy to do so.

I'm having a couple challenges that I'm sorting through but I'll start with the issue where sync's doesn't seem to complete.

In this scenario, I have 3 nodes all running version 1.0.125

Node 1 - Windows 7 Desktop PC

Share 1 - 23.7GB in 33,169 files (this is the original)

Node 2 - Windows 2008 Server

Share 1 - 21.1GB of the 23.7GB and 27,770 of the files sync'd

Node 3 - Windows 7 Laptop

Share 1 - 21.7GB of the 23.7GB and 27,998 of the files sync'd

This was happening with the prior client version so I tried the new version noted on the forums. I've broken and recreated the share on node 3 to no effect.

Cheers,

Ryan

Share this post


Link to post
Share on other sites

I have the same issue. The difference are about 700 mb between the original folder and the other 2 clients.

I´m running version 1.0.116.

Node 1: Windows 7 Desktop PC (Home)

Node 2: Ubuntu Server 11.04

Node 3: Windows 7 Desktop PC (Work)

Share this post


Link to post
Share on other sites

Same issue here with one client on Mac and the other on Debian Linux, both version 1.0.134.

What kind of logs would you need, both machines? Debugging enabled, I guess? Send them via email?

Tp7gEoftLdMzyAcBPM94BLIX0.png

Share this post


Link to post
Share on other sites

First, I want to express my gratitude and thanks for building this amazing tool! Side note, before I get into my challenges... I own a data center company in Seattle and if we can donate any server/data center resources towards the project I'd be happy to do so.

I'm having a couple challenges that I'm sorting through but I'll start with the issue where sync's doesn't seem to complete.

In this scenario, I have 3 nodes all running version 1.0.125

Node 1 - Windows 7 Desktop PC

Share 1 - 23.7GB in 33,169 files (this is the original)

Node 2 - Windows 2008 Server

Share 1 - 21.1GB of the 23.7GB and 27,770 of the files sync'd

Node 3 - Windows 7 Laptop

Share 1 - 21.7GB of the 23.7GB and 27,998 of the files sync'd

This was happening with the prior client version so I tried the new version noted on the forums. I've broken and recreated the share on node 3 to no effect.

Cheers,

Ryan

1.1.27 and same problem!

Share this post


Link to post
Share on other sites

I have the same issue. The difference is 351.8MB

Computer 1: Ubuntu 13.04 running BitTorrent Sync 1.1.42

Computer 2: Lubuntu 13.04 running BitTorrent Sync 1.1.42

As seen in this picture it shows that there is more to be synced in my music folder but upload and download speeds remain 0.9H4Y75K.png

Share this post


Link to post
Share on other sites

As seen in this picture it shows that there is more to be synced in my music folder but upload and download speeds remain 0.

Are any other programs currently accessing content within your /home/chad/Music folder, as this would explain the behavior you're seeing. If files are in use/locked by another process/application, Sync will indicate the amount of data to be transferred but won't actual begin transferring it until the files in question are released by whatever other process/application is currently using them,

Share this post


Link to post
Share on other sites

Do you use read-only or read-write secret for this folder? Do you see if other side wants to download the same amount as the first one wants to send? Also please enable debug log on both sides and check it for any errors.

Share this post


Link to post
Share on other sites

Similar issue here for one of my sync folders (others seem fine) so I'm interested in the outcome.

My situation. Several nodes involved:

1. Main desktop - Ubuntu 12.04

2. Main phone - Android 4.2.2

3. Main tablet - Android 4.2.2

4. Utility PC - Windows 7

Originally had an issue with a 12MB file and sync not finishing to node 3 & 4 seemingly just to that file. It has been persistant for the last few days since the original sync was established.

Share this post


Link to post
Share on other sites

OK I've had this problem too for some time now, I have enabled logging on both computers.

I have a folder that is over 15 GB and only 2 GB has synced and it has halted.

Where are the log files stored?

Share this post


Link to post
Share on other sites

Just joined the forum to post in this thread as I am also having the same problem, and it also concerns the music folder. Bittorrent Sync registers the new files (according to History), but doesn't appear to upload them. There's a 10.3GB difference in the size of the overall data being synced, although the destination computer only registers 2.1GB that needs downloading.

Interested to see the solution!

Share this post


Link to post
Share on other sites

I have the same issue with 271 Mb not being synced.

Is there a way to see which files do not get synced? I want to check if these files are locked.

I am using a read-only sync.

Share this post


Link to post
Share on other sites

I had a similar problem when syncing my win and linux machines. My linux machine is not using utf-8 but iso8859-15.

the folders where synced before using btsync.

since btsync can only handle utf-8 filenames it couldn't sync files with special characters from my linux machine - like üöäéèê. so it synced the files from win to linux. this led to the fact that I had those files twice on linux. tüst.txt and something like tüst.txt e.g.

the funny thing is that btsync was aware of those files on linux but couldn't sync them. It showed me +2000 more files and 1.5 GB more on linux than on windows - it also never stopped syncing although it didn't do anything anymore...

may be this helps?

Share this post


Link to post
Share on other sites

Same problem syncing between win/linux using 1.1.48 on all nodes. The share with problems contains files with special characters like æøå.

Log

lots of "Merge: will send files for ***" (many containing special characters)

..its aborting with

Merge: failed to verify signature of remote file ***, aborting

3GB of 3.8GB not syncing from win->linux

Share this post


Link to post
Share on other sites

Same issue here. Trying to sync 2.9gb of images between Android 4.0 phone and Win8 laptop. Latest versions of Sync on both. On my laptop it shows that there is only 942mb to be synced, and that's all it successfully synced. I ditched Dropbox camera upload for this but sadly it's not working...

Share this post


Link to post
Share on other sites

I'm having the same problem here, though not as severe as others. I have just one or two pesky files that refuse to sync among the 4 clients running BTS. I cannot isolate which files, among the 13GB, are not syncing. Look forward to a fix!!!!

Share this post


Link to post
Share on other sites

Same problem syncing between win/linux using 1.1.48 on all nodes. The share with problems contains files with special characters like æøå.

Log

lots of "Merge: will send files for ***" (many containing special characters)

..its aborting with

Merge: failed to verify signature of remote file ***, aborting

3GB of 3.8GB not syncing from win->linux

Could you please follow these steps ?

Thanks!

Share this post


Link to post
Share on other sites
Guest

I have the same issue with 271 Mb not being synced.

Is there a way to see which files do not get synced? I want to check if these files are locked.

I am using a read-only sync.

Hi, rene.

Will try help you.

Files do not get synced:

- files in SyncIgnor list.

- files are not permited to you.

Zero length files will be synced but will not be shown in GUI.

Share this post


Link to post
Share on other sites

I've found some solutions to my own problems. I have a mix of linux, OS X, and Win 7 here. The biggest problem has been with going from OS X or linux to the windows 7 boxes. However, there have also been problems with OS X to OS X. I'll enumerate the issues and what I did to resolve them.

1. OS X to OS X.... file names were too long.

In this case BTS was able to show me in the History tab that these files failed sync. This was on the receiving machine. The solution was to shorten the file names. They were indeed very very long. It's strange that the originating OS X machine had no problem creating the file..... but synching it was a problem. I also wrote script to find and identify the long file names. I shortened them manually.

2. OS X/Linux to Win7.... long file names

NTFS is much more restrictive with file name lengths. I had to find long file names/paths and reduce their size. This was a bit of a task as the windows client for BTS didn't give me much indication of which files it was unable to sync. In fact, the windows boxes indicated that they were in sync. Only the OS X and Linux boxes were complaining that there were bytes left to sync. I used the script mentioned in (1) to find long file names and shorten them.

3. OS X/Linux to Win7.... special characters

For sure I've had problems with : and \t (tab) in the file names. There were some others that I suspected but can not confirm. I wrote a script to strip out all the problem and suspected characters and rename the files on the originating OS X/Linux side. Once those file names were cleaned up, the sync with Windows completed.

If BTS could identify both on the originating client and the recipient client exactly which file were failing due to file names I would be a happy camper! :)

Share this post


Link to post
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.