[Dealing With '.conflict.' Folders]

noiime,

 

could you please check that "T:\" drive is added to the sync as "T:\" and not as "t:\" ? If not - this may be a root of the problem, when path of sync folder contains letters in wrong case.

[Security Big Bug?]

BTSync secret is base64-encoded set of bytes, so if you will try to encode your self-generated secret you will see the "real" secret being used by BTSync as private key.

 

So, if you want to generate your own secret its much better to base64-encode it before pasting to btsync.

 

As for your key - its len(166) is not a multiple of 4 and two last characters are ignored.

[Error Code 103 In Get_Folders Response]

Error 103 means that btsync can't identify the destination folder: ".SyncID" file is missing or this file belongs to an another share (content of ".SyncID" file differs from an expected)

[btsync inhibits disk hibernation / Interaction with .SyncID-File]

btsync (1.1.48 and 1.1.70) still doesn't allow my synology box to hibernate the HDD

Switching on the debugging option in the synology box and checking the logs.

btsync seems to write sync.data and sync.dat new every 10 minutes (the minimum disk idle time before the synology hibernates the HDDs is 10 minutes) even if sync.dat hasn't changed.

Also it seems to write settings.dat every 30 minutes, again even if these haven't changed.

I assume that these timed writes are just a precaution and these files are also saved should change actually happen.

Could the times when btsync automatically saves these failed be configured?

Matthew

Try to increase folder_rescan_interval in advanced settings.

[unc paths error]

why does BTSync not support UNC paths? i get an error trying to add a local pogoplug drive:

\\Fads1a58cc

drive works with all other software, please advise if this path can be allowed - declares an error. thanks!

brad

Could you please provide us an error message?

Have you tried pre-pending your UNC paths with "\\?\" - Please see this thread

Long-UNC paths should be prepended with "\\?\UNC\", "\\?\" prefix just tells WinAPI not to parse passed path and transfer it "as is" to the file system. This prefix disables MAX_PATH limitations. Each time u're adding a new folder to the BTSync it converts folder path to its long form, so adding prefix just disables conversion algorithms.

[.syncIgnore not ignoring the files]

To skip folder with its content u need to add 2 new rules to the .SyncIgnore:

folder

folder/*

This behaviour will be fixed in next releases

Slash before template (like "/folder") means that rule will be applied only for root folders(files)

[PIECE 0 FAILED HASH CHECK]

It's a known issue. The file content has been changed while its modification time wasn't, but sync uses modification time to decide whether rehash the file or not. This way sync stores an outdated file hash. As a workaround you may manually "touch" the file on the source pc to update its mtime and tell sync to rehash the file.

[Latest Sync Build: 1.1.70]

Hello,

we have just installed the update. Is it correct that UNC-Paths are no longer supported?

Thanks in Advance

Hi.

This bug will be fixed in next releases. As for now you may add long-UNC path, it starts from "\\?\UNC\".