WARNING: versioner: lstat ... no such file or directory

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:

 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
  1. You still haven’t specified which versioner you are using ?
  2. Have you switched the versioner type along the way ?
  3. Does the file with the timestamp exist in the versions folder?
  4. Is that a file you are trying to restore?
  5. Enable STTRACE=versioner and post the log line again (which will have a line number)
  1. Staggered
  2. No
  3. Not by that name. The referenced is the base filename (example.jpg) while the directory contains timestamped (example~20190103-145106.jpg) form
  4. I try to restore a file, which exists in the .stversions/directory/ folder. I may try one by one, or all by selecting diretory in the UI
  5. follows:
[ZILLL] 2019/06/18 14:13:21.144061 DEBUG: Versioner: Expiring versions [{kkk/IP 2015.pdf {0 63600387389 0x164dc20}}]
[ZILLL] 2019/06/18 14:13:21.144064 DEBUG: Versioner: File over maximum age -> delete  kkk/IP 2015.pdf
[ZILLL] 2019/06/18 14:13:21.144072 WARNING: versioner: lstat /path/syncthing/data/qwz/.stversions/kkk/IP 2015.pdf: no such file or directory

And the physical file is:

  File: /path/syncthing/data/wmm/.stversions/kkk/IP 2015~20180802-100304.pdf
  Size: 48092           Blocks: 96         IO Block: 4096   regular file
Device: fd0ch/64780d    Inode: 270277611   Links: 1
Access: (0640/-rw-r-----)  Uid: ( 1000/    grin)   Gid: ( 1000/    grin)
Access: 2016-06-01 16:16:29.000000000 +0200
Modify: 2016-06-01 16:16:29.000000000 +0200
Change: 2018-08-02 10:03:04.284463709 +0200
 Birth: -

Seems like a bug in the RC, can you open a github issue?

1 Like


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.