Recommended Posts



Found a weird error, the "date synced" column is quite a bit ahead, see the attached image. This instance runs on a beaglebone black, which loses the correct time after restart. NTP service is running and currently the system time is correct though (and has been as far as I can tell as long as btsync is installed). Maybe btsync starts before NTP and this messes things up?


Seems not to affect sync, but still something to fix I suppose.




Link to post
Share on other sites

@Bitwise, @tommi

It might indicate that certain folders contain files with incorrect modification time (in future). I suggest finding these files and fixing mtime as it can bring issues in future (they will overwrite any other files with same name on other peers as they are always "newer").

Link to post
Share on other sites

@RomanZ   Thanks for the suggestion.  I found two files with mtimes in the future.  It appears that clockworkmod creates files with timestamps in the future.


Can you explain a little more about why files with future mtimes will cause BTsync to exhibit this behavior?


I archived both files, and now there are no files with future timestamps.  BTsync did not adjust the dates in it's GUI.  I restarted BTsync, but no effect.  I rebooted, but still no effect.  The BTsync GUI still appears as above.

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.