What is sync.dat.new.n.bad?


Recommended Posts

I just noticed in the BTSync directory on my Linux system I have a few sync.dat files that are curious:

  • sync.dat - timestamp 2-May
  • sync.dat.new.1366842849.bad - timestamp 24-Apr
  • sync.dat.new.1367459505.bad - timestamp 1-May
  • sync.dat.old - timestamp 2-May

Any ideas? I'm concerned specifically about the "...bad" files.

I also have one peer saying it has 6.6 GB left to upload, but the (BTSync-reported) file count matches on both ends and my end says it's in-sync (no transfers pending). A restart of BTSync on both ends had no effect, even after it showed indexing progress and completion.

Link to comment
Share on other sites

The bad files probably won't delete themselves, you're expected to investigate what's wrong with your system (if this wasn't alpha software).

Having said that, a rather common error with the Linux exes seems to be to put the .sync directory inside the shared directory.

This can cause really bad problems when the two clients overwrite each other's files.

Have you done that ?

Kos one for the issue list, you need to make sure that the client is okay (or aborts) if the ".sync" directory is inside the share.

Link to comment
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.