Moving the location of the temp file?

[RChadwick (Robert Chadwick)]

I’m running Syncthing on an odroid C4 with 32GB emmc and an 8TB USB connected drive. After installing and running Syncthing for a half hour or so, I get this error:

2025-09-09 03:01:38: Saving config: write /storage/.kodi/userdata/addon_data/service.system.syncthing/.syncthing.tmp.793318938: no space left on device

Is there a way I can configure Syncthing to store temporary files on the external 8TB SSD?

[sektor2sync]

Hi, this is potentially not about a temp file because of “Saving config:..” but you can copy your syncthing configuration folder to your external disk and link to it or use one of the command line options at startup to set the config/db directory to the external disk. Command line options can be found here.

EDIT: UPS, I didn’t saw the tmp extension. You may want to look at this thread or this fix and retry with the current version as it may be fixed already.

[RChadwick (Robert Chadwick)]

Thanks for the response. I probably should have clarified I’m running v1.30.0 as I’d like to wait a while for 2.x

[sektor2sync]

I think I totally misunderstood the case so I’m sorry for the noise. The case you describe seems unrelated to what I’ve wrote since /tmp is not used. I’m not sure if syncthing on kodi can be configured. If you can configure it, change the config/db directory to the external drive may help. Check the plugin preferences in case this option is offered.

[wweich]

The temp files must be on the same filesystem as the directory beeing synced, as the rename to the original filename has to be atomic.

[chaos]

I believe you are incorrect. The file …/.syncthing.tmp.793318938 isn’t of the form .syncthing.original-filename.ext.tmp as described in Understanding Synchronization — Syncthing documentation . I believe this is a different Syncthing temporary file, not a file that is in the process of being synced.

[wweich]

I ignored the "Saving config” part . The config file has only a few KB, if there is not enough space for that, than you have other problems. It is very likely, that the atomic rename also applies to the config file.