RomanZ

@mneiger I still would avoid doing so. Sync stores it's own change time in DB separately from the file. For example, if you move old file version on top of a newer in Sync folder - Sync is going to deliver it everywhere, because it's change time is the most fresh. This mechanism is not going to work with dual boot, and some files may sync in an unexpected direction.

@0mikeyj0 It should be rather quickly - unless some files are actually ignored / cannot be synced. Any message in UI about locked files? IgnoreLists are the same on all machines?

@micnolmad Yep. Or mail me.

Damen, Sync must be running on 2 computers (requester and approver) to actually get approval as your peers want to talk directly to actually exchange keys.

@hungarianhc Check if your ignoreLists are the same on these NAS and wife's computers. @BitDuck Actually this is something that was intended to fix with the .99 build. Did you perform an upgrade or made a fresh install?

@mbob Office may propose to recover files if it encounters some temp files next to your document (and suggests that office itself was not closed correctly). So, there might be some issues on file level - which we are trying to resolve in this topic, but not on file content level.

@zeropluszero Sync guarantees that it delivers files without any changes - it controls hashes of the files. The only confirmed case of file corruption I know of was bound to HDD failure - HDD itself provided corrupt data. Could you please check health status of your peers hard drives?

@Hakker This is something Sync actually does (roughly). Though note, that it takes time to read 3000 files and hash them. @ICE When you re-add the folder, Sync completely "forgets" about all the files and adds them from scratch. And to do so - it needs to hash all of them. If sync does it way slower than HDD bandwidth (usually it is limited by HDD read speed, as CPU is powerful enough to hash data much faster than read from drive) - it looks to be a bug and to be investigated. Otherwise - it is app design.

@sunylat I don't remember that we've fixed some crashes in 1.4.99 comparing to 1.4.93 - so it is very unlikely. Can you please send me a crash dump?

Marc, I doubt it is going to work. At least paths on Windows and Linux stored in DBs are not going to be compatible (maybe something else I did not think of right now). So I advise to avoid using same Sync DBs on dual boot systems.

@brand, Please take a look at this article. Let me know if you have further questions.

@jdyer Thanks for info, doc adjusted.

@sfmcnally There was a big number of changes and optimizations on the core, so it can't be tracked easily. The 1.4.99 build contains a couple of fixes that should fix your situation. Did you re-add the folders and it is still not working? If yes - we'll need your debug logs to understand what is not working in your environment.

@all, We've got a possible for for this issue and experimental build with this fix. If anyone wants to test it - please acknowledge here or PM me.

@jdyer It looks to be different case. In your case Sync is simply indexing files in folder that is added to ignore list (which is quite normal as folder is already in the tree), while in @ms2oo8 case indexing never completes. @ms2oo8 If you are willing to help us in debugging this issue - well need a debug logs from your computers.

@jdyer We are answering all tickets delivered to our ticketing system, though ours support is not working 24/7 - so please be patient and we'll do our best to assist you. Forums are not primary goal for support and mainly exists to give opportunity to community to help each other.

@scotepi Sync designed to detect file movements (rotations in your case) within the boundaries of a single sync folder. Do I understand correctly that it fails to detect file movements within one folder? If yes - can I plz get your debug logs? I would be really happy to catch this issue!

@advhound I'm not proficient in building such setups. Though I could advise to be careful with passive HDD cooling: any HDD has a bunch of mechanical parts which is very temperature-sensitive and every degree matters against the term of HDD service.

@micnolmad Let me know if you are willing to debug and find out why data is not syncing in your case - i'll supply you with instructions.

No, it is not possible. Older interface simply does not exist for 1.4. Do you want to downgrade because if UI or there are something else that is not working well?

@all, We've released a new build for iOS 1.3.103 today. It has fixed issues with camera backup, permissions, etc. If you upgraded and have some issues on 1.3.103 with syncing your folders - simply readd your folders.

@dwmass Yes it is possible. Remove the folder from Sync on your phone, move your files, then add the folder again by scanning same QR code as was before. Sync will re-index files, realize that they are the same as on PC and won't resync.

@frank@btsync Sync might put it in the queue - but please note, that files will be removed from queue rather quickly, with no actual file body transfer. Sync will remove them from queue once file is hashed and hash value compared against the tree it receives from other peers.

@ms2oo8 1.4 has advanced mechanism of detection of moved files, so if file movement happens within same sync folder - it should not be resent, but moved instead. I tested it in my lab - it seems to be working fine with no extra transfers over network. Can I get your logs and the name of affected file to track down what happens?

@zeropluszero Next update = next public update. We do not plans any more experimental builds for this issue.