Lately I get plenty of warnings on startup that various .stversions have “no such file or directory”. It is a premanent message: comes up every restart, and there seem to be no hint as to how to fix it, or what’s actually wrong. (My guess is syncthing believes something to be in .stversion while it isn’t.)
Syncthing also seems to be pretty confused about saved versions: for example a staggered dir had some stuff deleted, manually re-set (2017) and then deleted again (2019), and the GUI restore wants to restore files from 2017, while the directory contains files from 2019 (file~2019xxyy…). Obviosuly it fails to restore them.
The version time is the mtime of the file, the date in the filename is the mtime of the file before it was archived. You should post whole errors not some small excerpt that makes it impossible to understand where it’s happening.
Also, version information and other information would be useful.
Sorry, that was the full error, apart from the specific path:
[ZILLL] 2019/06/18 09:27:43.941586 WARNING: versioner: lstat /path/storage/syncthing/data/myfolder/.stversions/test1/star_trek_selfie-leVar_Burton.jpg: no such file or directory
...and lots of similar...
The GUI shows a lightly different format of the same as:
NOTICE
2019-06-18 09:27:44: versioner: lstat /path/storage/syncthing/data/otherdir/.stversions/else/evenmorepath/note: no such file or directory
...and lots of similar lines...
While this is v1.2.0-rc.1, Linux (64 bit) the problem is present for some time now; my logs go back to
2019/06/11 20:25:28.692200 WARNING: Automatically upgraded to version "v1.2.0-rc.1" where it first shows and it seems it was not present before rc.1.
You are right that the mtime is from 2017. I do not seem to have any error about the failure of restore, apart from the UI message about failure:
Restore Versions
Some items could not be restored:
teszt/read.me version not found