Unresolvable "Out of sync" after full disk

I have device A, which has a folder in “Send Only” mode. Another device B is syncing this folder normally. (Device A is a phone and the folder is it’s camera folder, so I’m syncing photos to my laptop B.)

I added a file to device A (took a photo). However, device B had too full disk so the syncing failed. I freed some disk space and lowered the threshold of free disk space that Syncthing requires. Now there’s plenty enough disk space. However, the folder still stays “Out of sync”:


I’ve restarted syncthing on both devices, tried pausing and unpausing and rescanning the folder on both devices. Nope, nothing helps. The folder stays “Out of sync” on device B, but still this device shows on “Remove devices” section that it’s “Up to date” with that device.

Also, I thought there should be “Override changes” button visible on device A in this case, but there isn’t. Device A is Android device and I looked both the normal Android view and web GUI.

How can I force sync? Device A still has this photo that device B hasn’t received. Device A should just send it… Any ideas?

(Just for reference, here’s the GitHub issue I opened but which was closed and I was directed to this forum: https://github.com/syncthing/syncthing/issues/6423)

1 Like

It still says “insufficient space” in your screenshot. What’s the details on that error, when you mouse over it?

1 Like

It says the same thing: “syncing: insufficient space in basic /home/jluttine/.syncthing/folders/Camera”.

What is the MinDiskFree setting on that folder and the output of df -h /home/jluttine/.syncthing/folders/Camera?

$ df -h /home/jluttine/.syncthing/folders/Camera
Filesystem                   Size  Used Avail Use% Mounted on
/dev/mapper/luks-nixos-root  228G  212G  4.2G  99% /

Minimum free disk space is 500 MB.


This is for where the database is stored, not the folder. There are two separate settings, one for database, and one per folder.

1 Like

I have only two partitions: / and /boot. So everything syncthing related should be under that / shown above.

$ df -h
Filesystem                   Size  Used Avail Use% Mounted on
devtmpfs                     797M     0  797M   0% /dev
tmpfs                        7.8G   84M  7.8G   2% /dev/shm
tmpfs                        3.9G  6.7M  3.9G   1% /run
tmpfs                        7.8G  408K  7.8G   1% /run/wrappers
/dev/mapper/luks-nixos-root  228G  212G  4.2G  99% /
tmpfs                        7.8G     0  7.8G   0% /sys/fs/cgroup
/dev/sda1                    477M   92M  356M  21% /boot
tmpfs                        1.6G   12K  1.6G   1% /run/user/1000

Well, this is weird. It suddenly synced now!

My hypothesis: I had a higher threshold for the minimum free disk space when the syncing originally failed. I then lowered the threshold and freed some disk space (but maybe not enough for the original threshold).

A moment ago, I freed some more disk space, and after that it apparently synced. So is it possible that it retried syncing only after I had free disk space more than the minimum requirement during the original sync failure?? That is, as if changing the minimum requirement had no effect.

1 Like

Yes, it retries stuff periodically.

It should have picked it up immediately: Changing the minimum required disk space restarts the folder, which then retries the sync with the new setting.

It had been in out of sync state for a few days after I lowered the threshold. After that I had also restarted syncthing on both devices and pause&unpaused the folder on both devices, trying to trigger syncing.

But did you actually lower the threshold for the folder? Your Screenshot shows the threshold for the DB.


@wweich Ah, now I understand! Yes, sorry, I lowered it only for the database apparently. I wasn’t aware that there’s a different threshold configurable for each folder, but indeed it makes sense. So, it was just my ignorance. Thanks a lot everyone!


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