I’m hitting the same issue that several folks here seem to have had, but I have a reproducible case that I haven’t seen mentioned here (sorry if I’ve missed it).
In short, I’m syncing a directory of photographs between two computers over a somewhat flaky & slow ADSL line. Syncthing works great, however if I rename images (with exiftool, which I think does a rename() under the hood) while the sync is progressing, then syncthing seems to think the original & now deleted files still need syncing. Receiver shows up in Sender’s devices with the usual “Syncing, 95%, 0B” status, and on the receiver, the deleted files show up as needing sync but failed with “no such file”. None of these files are affected by any .stignore rule.
In any case, the syncing of actual files is performed flawlessly, rsyncing them shows no changes required.
To solve the issue, I can delete & re-add the folder on either end, or reset the DB on one of the two ends. Is this considered poor use of Syncthing, or is this a (admittedly cosmetic) bug? Any tips on how I can prevent this from happening?
Receiver “failed items”
Receiver’s “device” entry “out of sync items” on Sender (a.k.a kdmhome) (i.e. recv’s listing on bottom right of web ui on sender)