Stuck at Syncing (95% 0 B) after cutting file that was not accessible at remote. Solved.

MAY THIS BE OF HELP TO ANYBODY WHO IS TRYING TO FIX SYNCING (95% 0 B) PROBLEMS

Hey,

I know this issue has been around since at least 2 years now. I encountered it again yesterday. I solved it for myself without reset of deltas. Maybe your setup is different, so maybe you need to do different things, but the following is what happened to me and how i solved it:

My setup:

The ones that were online at the time:

  • [GTMM2P] Windows 10, Synthing 1.18.5 via SyncTraizor:

    Machine with Syncing (95% 0B) error and from which i operated and moved a file.

  • [BJGC44] Windows 10, Syncthing 1.18.5 via SyncTraizor:

    Remote with original file and that was pushing the file to the other two.

  • [F4MFRU] Linux Fedora 34/35, Syncthing 1.18.4:

    Remote that was maybe still in process of syncing (because slower pc).

What was done that led to the current state:

  1. While working from [BJGC44], my brother put a file (“Professional2019_Retail-DE.img”) into: E:\server-ALLE\Simon\

    This file was large (>3 gigabyte). It took a while to sync.

  2. While working from [GTMM2P], I waited until the sync was done. Everything was fine on my end. All folders said “up to date” and all devices were “up to date”.

  3. Shortly after the file was done, i went to the folder and cut the file ("“Professional2019_Retail-DE.img”) and pasted it in "E:\server-ALLE\Ertel Devices\2014 Simon Desktop GA-H81M-S2PV\00 Microsoft Office 2019\"

  4. Syncthing started to sync

  5. Syncthing could not finish the sync and stopped at syncing (95% 0B).

  6. When i checked on [BJGC44] (my brothers pc) the next day (today) it turned out, that he had accessed the image via a virtual dvd-drive, hence the computer was blocking other programs from accessing the file. Interestingly, Syncthing had created a duplicate of the file in the folder i had pasted the file in. So to make this clear: Now we had 2 files at [BJGC44] but only 1 file at [GTMM2P].

    Here the error messages i could see in Syncthing:

  7. I removed the blocked file from the virtual drive on [BJGC44] and therefore it was now possible to access the file normally again.

  8. I rescanned all folders on [BJGC44]. The error message was still there.

  9. As there were still 2 files on [BJGC44], i manually deleted the file in the path that was giving the error message.

    Check out the log file:

    [BJGC44] protocol after deleting the file.txt (41.3 KB)

  10. I rescanned all folders on [BJGC44]. I can’t remember if the error message was still there or not.

  11. I restarted syncthing on [BJGC44]. All error messages were definitely gone.

I am happy again.

MAY THIS BE OF HELP TO ANYBODY WHO IS TRYING TO FIX SYNCING (95% 0 B) PROBLEMS

2 Likes

Thanks for posting that – but I cannot figure out what you are saying is the solution. Would you mind responding with just the steps to solve the 95% 0B problem set out alone?

I repeat this worked for me, but may not work for you, as 95% 0B Error might be triggered by multiple causes. I am just a user, i don’t know about the code. Above you see what triggered the error for me personally.

Here the short solution in different wording:

  1. Inspect remote device(s).

  2. Check if there are files that are currently in use or locked (on remote); (File locking - Wikipedia).

    • If yes, Unlock the file.
    • If yes, check if files had been moved to a different location on the harddrive (or deleted or modified) while the file was locked on the remote drive.
    • If so, Manually delete any duplicated files that were created by Syncthing because the file was locked. This is important. Even if the file was unlocked, as long as the duplicate is there, Syncthing will show the error if i remember correctly.
  3. Sync / Restart Syncthing.

Done.

To trigger the error it basically comes down to trying to manipulate (a large?) file at the same time with two different devices, which makes Syncthing go woooo.