finisher: file modified but not rescanned; will try again later


#1

Coming from https://github.com/syncthing/syncthing/issues/4353#issuecomment-341660539, I installed v0.14.40-rc.4.

I removed my synced folder and added it again. I constantly get following output:

finisher: file modified but not rescanned; will try again later

However, the file named is not modified on either side.


modified but not rescaned. will try later... again
#2

Renaming the file on the sending side solved the issue for me.


(Audrius Butkevicius) #3

If the case of the foldee changed, this could happen.


(Spo0okie) #4

i have the same problem. Is new version fix this?


(Lee) #5

Same problem here as well. Unfortunately I have over 692 files in one directory that have the error message, so renaming that many files is not an option for me. The strange thing is that I have three other Syncthing servers that are synchronized with the same folder and those three servers are all showing up to date.


(Audrius Butkevicius) #6

You can try renaming the directory.


(Lee) #7

Thanks I had not thought of that. Would I also need to change the shared folder path to match the new name?


(Audrius Butkevicius) #8

Not sure I understand. If all the files within some subdirectory in a folder, then you can rename the subdirectory. If they are at the root of the folder, or scattered, you might want to upgrade to the latest rc which should have this bug fixed.


(Lee) #9

I am sharing the root folder which is named HBT Service, however, the problem files are in multiple folders which are sub folders inside the HBT Service folder. There are 109,208 files and 15,175 folders inside the HBT Service folder. I am using SyncTrayzor and do not see an option to install the RC versions. I may have to just wait until the 28th when the RC is officially released. These are production machines with 3.7 million files being synchronized, and the root synchronized folders are mapped to about 100 employees. I am afraid to experiment too much.


(system) #10

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