As I’m new to syncthing, I’m unsure what to check in the failed files.
One has the status: “filename is invalid”
The rest has “peers who had this file went away, or the file has changed while syncing. will retry later”
As this sync is send only on master and receive only on the slave, I do not understand why files that “went away” would give an error. If they are no longer at the sender, the receiver should not care…
That being said, I’m not sure how to deal with these errors - input would be appreciated
Invalid file name implies that the local filesystem does not support the characters in the file name.
Peers who had this file went away usually means the file changed after sync was started, potentially because you atarted syncing before the scan was finished.
Note the difference in file count between the master and slave.
Also the master thinks the slave is at 82%, but slave thinks it’s at 99%.
Is there a trick to getting the slave to re-sync with the master?
Otherwise I’m considering removing the entire directory from the slave and starting from scratch - would be much nicer to be able to get it to sync the renaming files.
Is there any change on the receiver (local/global state, folder status, …)? That the status is syncing not out-of-sync and cpu usage is high(ish) looks to me like it is still working on exchanging and comparing file metadata - if this is after initial setup it can take quite a while. If that’s not the case (well anyway), please check the logs.
The status of the slave changed between syncing and out of sync. New items were synchronised from the master to the salve, but not the missing items.
The clients on both master and slave have now auto updated to the new version (v0.14.52) and now it seems to have resolved it self
Unfortunately it also seems to have started from scratch in some regards, as the slave is now also uploading everything it has locally to the master - this does not make a hole lot of sense as the master is send only, and the slave receive only. I guess all files received at the master will just be ignored.
I believe this will take several days to complete - not ideal in regards to bandwidth usage and time spent syncing.
I thought the remote status on the master meant the remote is uploading everything, but judging from its speed I no-longer think that is the case.
The slave syncing has slowed to a crawl after the client was updated, but it is still syncing. I guess that when the remote status on the master has reached 100% the sync speed will return to normal.
I will not waste more of you time for now, but keep an eye on it to see if it returns to normal.
Status does not indicate actual transport of data. On upgrade the stored metadata is reset, so what the device are doing right now is exchange and compare each others metadata - as long as the data is the same no file data is transferred. However as you are syncing quite a lot of data, the transfer of the metadata itself will be noticeable. If you also have big files, it would probably speed things a bit up to enable useLargeBlocks (https://docs.syncthing.net/advanced/folder-uselargeblocks.html).