That’s bad stuff. I suspect one of the components in that full path is a symlink of some kind and the filesystem watcher gets confused and we accept a path that we shouldn’t…
The first win machine is on read-only and the second win machine showed the error.
I don’t use any symlinks in this folder. At least no unix-type symlinks.
There might be Windows type “junctions” in that folder (by default) though.
But i haven’t seen this before and using this setup for a while now.
I guess for now - if nothing breaks we can just ignore it … unless of course you have an idea what the problem is an can fix it easily.
Ok, this is happening more often now and seems to prevent the folder from syncing.
Also syncthing seems to use up a lot of CPU (probably caused by this).
All other folders are up-to-date.
So i will go for the dev-build you mentioned. Thanks again!
With the new version (without resetting the index though) it still happens:
2018-04-07 23:06:11: Dropping index entry for Skype/C:\Users\User\AppData\Local\Packages\Microsoft.SkypeApp_kzf8qxf38zg5c\LocalState\94db313a-c5fd-4aac-8ddf-5b02cfb3c76f_20180406_113030260.jpg, contains invalid path separator
2018-04-07 23:12:21: Dropping index entry for Skype/C:\Users\User\AppData\Local\Packages\Microsoft.SkypeApp_kzf8qxf38zg5c\LocalState\94db313a-c5fd-4aac-8ddf-5b02cfb3c76f_20180406_113030260.jpg, contains invalid path separator
But it seems to be only this one file though. But of course could be that the first file covers the rest of them … like “abort on first error” or so.
When i try this: syncthing quits instantly without any output.
I have seen this command somewhere earlier, did you mean this one?
syncthing -reset-deltas
I just found: --help actually lists this command.
Do i have to do this while another syncthing instance is running?
Or do i have to start syncthing normally after doing it for it to take effect?
Ok, after restarting it now, syncthing scans all folders.
Looks like the reset worked. Well then … let’s see if the problem is gone now …
This might take a while. I have a lot for it to scan.
Bad news: Does not seem to help.
Even before the scans finished i got this again:
2018-04-07 23:53:20: Dropping index entry for Skype/C:\Users\User\AppData\Local\Packages\Microsoft.SkypeApp_kzf8qxf38zg5c\LocalState\94db313a-c5fd-4aac-8ddf-5b02cfb3c76f_20180406_113030260.jpg, contains invalid path separator
2018-04-07 23:57:26: Dropping index entry for Skype/C:\Users\User\AppData\Local\Packages\Microsoft.SkypeApp_kzf8qxf38zg5c\LocalState\94db313a-c5fd-4aac-8ddf-5b02cfb3c76f_20180406_113030260.jpg, contains invalid path separator
.
Version: v0.14.46+32-gcf4d7ff, Windows (32 bit)
One more idea: Do i have to update all clients?
Or would it be enough to do this on the one with the errors?
p.s. it’s probably unimportant, but i just noticed: the dev build is 32bit, before i had 64bit.
You probably have to run the dev version on all devices and reset the index/database on all devices simultaneously (stop all syncthings, reset all databases, start all syncthings.
I don’t think a simultaneous reset everywhere should be needed as these index entries are dropped and this not accepted by other devices. More likely the underlying problem isn’t actually fixed. We should look hard at that before the .47 release next week…
Isn’t the dev build run on the wrong device? Lets say the ...Dropping index entry... log lines are observed on device A. This line is logged on an incoming index (update), thus the file info with the incorrect path was introduced on another device (B). Therefore resetting the database and using the dev version should be done on B. If the original cause is fixed (I still assume yes), we’d need to do another db transition filtering these files out (or fixing them up if possible) to get rid of them for everyone - self-healing db would be wonderful