1 file, Syncing (95%, 0B)

[mar2112 (michael)]

I have one deleted file that is trying to sync. The file does not exist on any of the computers or phones within my syncthing network.

The issue is only on my raspberrypi. All other systems are correct.

The first screenshot is from my rpi and shows that there is 1 file of 0B “Syncing”. FWIW, the file originated on my phone.

The second screenshot is from another computer on my network which shows no issue.

Any help to get rid of this annoyance is greatly appreciated.

[vacari]

@mar2112

ync

I have been a happy user of Syncthing for over 6 years now. I am truly grateful for the great work of the development team for developing something truly wonderful. If I had to point out one single problem with it, it would be that during all this time, I have always had this issue and they have never been able to fix it. I have about 30GB of data synced between 5 PCs (all Windows) in different locations and edited on all endpoints. This error happens quite frequently. Since I have OCD, this annoys me a lot and I have never found a way to fix it, except by PHYSICALLY deleting the folder and waiting hours or days for it to resync or by rewriting/recovering backups of useless files and deleting them again. Just today, after a disk full that prevented about 2,000 files from replicating, when I deleted them, one of the stations (which does not have the folder and files) continues to see these ghosts.

I know it’s not as simple as it seems, but I think it shouldn’t be impossible to do some of the following options:

1- Create a resource to mirror the DB of another device chosen by the user (like the real one), or;

2- A resource for the user to Delete the phantom entries from the DB registry (which are certainly no longer anywhere);

3- A resource for the user to ask to physically re-examine the folders on the problematic device in search of these files declared as OUT OF SYNC, that is, look at the Windows directory and understand that the file no longer exists on any of the endpoints and automatically fix the DB.