Testing OC currently. Syncing of documents seems to work great. I created an external share and set it up to sync but every minute or so it prompts that a backup was detected. There was no restore, and the files in question are old files. If I remove the sync target and re-add it does the same thing and always for the same files. The external storage is a windows 2008r2 share.
I tried using an older version of the client to see if that made a difference (it didn't).
I tried deleting and recreating the external storage location on the owncloud control panel, but that also didn't resolve the issue.
I've confirmed that time settings are correct and synced between owncloud server, client, and windows server.
This issue persists on multiple clients (tested on desktop and laptop).
Is there any way to find out WHY it believes these documents keep changing? Is there anything that can be done to resolve this?
Its a classic "works for me". So in order to help anybody will need a proper description how to reproduce with all the version numbers, config reports and log files in question ...
Hiya @degol as it surely has to do with what's happening under the hood of the Desktop Sync Client, what it's happening is going to be in those logs; here you have the docs: https://doc.owncloud.org/desktop/2.2/advancedusage.html explaining how to get to them.
I see in the log its complaining that the dates don't match, when I look at the Modified stamp on local and remote, they are off by 1 second. Any thoughts on why that is happening? But its only happening on 23 of the files out of the 1,000 or so in the current sync target? And it never fixes itself, its consistently the same 23 files are off by 1 second every time they are copied down.
Also if i manually copy over one of the trouble files, the local does now match the timestamp of the remote. But only if i copy through explorer, not if I allow owncloud to sync it.
I updated the client to the newest nightly, but the same thing is happening. When it syncs certain files (always the same ones), it syncs them as being 1 second newer than the file on the server (not all files in the folder, just some). Then it continuously resyncs it and replaces it (the newer nightly at least doesn't prompt and hold up all of the other syncs from running).