Sync 2.6.3 silently dies on large directory

Recommended Posts

I've been successfully using Sync (5 user license) for a long time on several nodes, one is Windows 10 Pro and others are various ARM boards running armbian (2 x Odroid HC2, one PCDuinoNano, 1 Linksys WRT1900ACS running openwrt + debian chroot).

A few days ago I decided to let Sync handle my photos directory which until now was synced by hand (and FreeFileSync). This is a ~500GB directory with ~62K files and ~1400 subdirectories. ~50% of the files are ~6MB JPEG and the other 50% are ~23MB Canon RAW files. None of my previously shared directories was even remotely close to that size by a factor of 10.

The folder was shared as an "Advanced Folder". I don't know if this is significant, but a few of the subdirectory names contained international characters. I think this shouldn't matter, as I previously had filenames with international characters, although not a directory name.

After setting the sync from a Windows machine running 2.6.3 as a service, into a single Odroid HC2 node, I noticed that the sync has stopped. I also noticed the Windows GUI has dies and further check shows that the service is indeed not running. restarting the service has not helped, as it kept dying within minutes to hours.

Earlier I also noticed the service dies on the WRT1900ACS, but I attributed the failure to the relatively low RAM on that router (512MB) so I simply disabled this specific folder on it. However, the Window machine has 16GB RAM and should not crash.

I enabled logging, but the log files shows no special messages, i.e. all the log lines have appeared earlier in the logfile. There was no line indicating a service crash. It was just like the log was cut off in the middle of the operation.

Any help?


Link to post
Share on other sites


I paused sync on both sides, allowing the node where I added the original folder, to finish indexing.

After it was done indexing, I reenabled sync on both nodes, and so far it seems to be syncing fine for the last hour or so, as it would crash earlier ~13 minutes after I started up the Windows Service on the original node.


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.

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.