Out of sync with File modified but not rescanned error

Hi all,

First of all, thanks for this great software. Together with the wonderful native iOS /iPadOS Synctrain app from @pixelspark and MacOS client by @xor-gate it has been a great replacement for Nextcloud overall.

However, I still have an issue with my setup, which drives me a bit crazy. I have regular cases of devices crashing in “Out of sync” state with a bunch of files showing an error saying `syncing: finishing: checking existing file: file modified but not rescanned; will try again later`.

I have tried to read all topics showing the same error but didn’t find a way to have these issues stop. I always use the same way to “unstuck” my system : rename the problematic files, wait for a few minutes, then name them back to their original names.

The error is always with the same three types of files : .docx, .pages and .latex, all after having been modified from the same Mac. It seems that my issue is more likely to happen when I update one of these files with very quick and regular saves.

Any advise ?

Can you post logs, syncthing cli debug file, and syncthing debug database-file output for a file that is suffering from this, while it’s suffering from it?

Sure :+1:

I’ll do all that the next time I get a corrupted file

Hi @calmh it happened again so I’m now in a situation to extract the required debug outputs. Shall I send these to you by PM ? Thanks again for the help

Ideally post them here but otherwise yeah sure

logs (4.3 KB)

debug_database-file (80 Bytes)

cli_debug_file (2.8 KB)

I hope it corresponds to what you need. If not tell me ! Strangely (or maybe not?) the `debug database-file` had an empty output. Thanks again for your help, I hope I can get rid of these errors.

Yeah that means it didn’t get the expected parameters most likely. Given the output from the other files you should be able to say

syncthing debug database-file Documents Cadeaux

(it’ll partial-match on the filename)

Nope, no matter what I do I get this same empty output with only headers… ?

Odd. My best guess for the root cause is that it’s something to do with the syncing of the extended attributes, maybe they change on every read for some reason, or are not updated correctly in Syncthing when it rescans. You may be able to confirm/deny by disabling syncing extended attributes, if that’s an option for you.

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