Syncthing randomly deleting folders

Syncthing has been randomly deleting folders and it’s pissing me off. I have a raspberry pi synced with my laptop and from time to time, I notice stuff missing and find out that it was syncthing that “decided” that I didn’t want it anymore. I still have it in .stversions but this definitely needs to be fixed. What the hell is going on?

syncthing v0.14.48 “Dysprosium Dragonfly” (go1.10.2 linux-amd64) deb@build.syncthing.net 2018-05-14 06:53:06 UTC [noupgrade]


Supposedly, the latest deletion occured today at 8:09:04 but I can’t find that time in the logs. The most recent logs are:

2018-07-03 07:55:24 Disconnected from relay relay://37.120.167.213:22067 2018-07-03 07:55:34 Could not connect to relay relay://188.226.140.237:22067/?id=AD7LXZA-RNNKKJK-YE6HFKU-XB2X6DL-DRGLQRH-2BSWISR-X4ED7UB-MS6J3AW&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 188.226.140.237:22067: i/o timeout 2018-07-03 07:55:44 Could not connect to relay relay://185.147.80.104:443/?id=VEBKIQ3-5QKYJXK-AK6H656-XY5GSHV-NGFUDA7-FPX3QMH-IV5YBMT-Z2UDAQK&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=4096000&statusAddr=:22070&providedBy=: dial tcp 185.147.80.104:443: i/o timeout 2018-07-03 07:55:54 Could not connect to relay relay://213.239.217.18:22067/?id=2OCEWX7-ILPTFPX-PALEW7F-M3FK6OS-XBDPLX2-YODZHBF-V2XWLNH-4WICZQC&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=spaam - spaam.se: dial tcp 213.239.217.18:22067: i/o timeout 2018-07-03 07:56:04 Could not connect to relay relay://164.132.51.252:22067/?id=G6M3ARK-XCJZOY5-TRMXJOE-VMAOLQ3-QSY2ZBN-C3KW2WC-6TWFS3K-DDKEPQZ&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=31457280&statusAddr=:22070&providedBy=: dial tcp 164.132.51.252:22067: i/o timeout 2018-07-03 07:56:14 Could not connect to relay relay://46.105.126.214:22067/?id=3YRKSJ2-YQMBIK5-QLTJDRI-WPHIYXN-SFL6DNI-XJUORWP-H5MGQVL-V7O5PQP&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 46.105.126.214:22067: i/o timeout 2018-07-03 07:56:24 Could not connect to relay relay://178.32.221.151:22067/?id=DQTVSC2-GVNRCVJ-BM3YNZF-QJS5QM5-4JID3CM-HNLWYIZ-SYKTODV-PDX4ZAE&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=500000&statusAddr=:22070&providedBy=fhransuski-lacznik: dial tcp 178.32.221.151:22067: i/o timeout 2018-07-03 07:56:34 Could not connect to relay relay://195.37.209.183:443/?id=TS7ZNKH-AUXS3SQ-M4AB3RZ-NSE6S7M-ZSRVF7T-LEAPYIN-242XD7V-RMBEFQ6&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=4000100&statusAddr:22070=srs.mpim-bonn.mpg.de&providedBy=mpim-bonn.mpg.de: dial tcp 195.37.209.183:443: i/o timeout 2018-07-03 07:56:44 Could not connect to relay relay://145.239.234.88:22067/?id=LYKW7VM-ALL67JQ-SP5WO3T-AJSWJHR-EMGBXZI-K3D7PJP-DJQSQ7N-SQGQUQQ&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=Arcanite Solutions: dial tcp 145.239.234.88:22067: i/o timeout 2018-07-03 07:56:54 Could not connect to relay relay://94.130.123.126:22067/?id=7YW3IXH-SKCUOPT-V5W7JXQ-5MSIRB3-FLYZTSG-FF3MAAK-OGMY6X2-EVKKEA7&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=Deka: dial tcp 94.130.123.126:22067: i/o timeout 2018-07-03 07:57:04 Could not connect to relay relay://212.25.15.128:22067/?id=YRB2IWT-7R23EWJ-3CMK5IQ-TY5U24F-ND4O25S-UZI4BE2-33TTB3U-BUHGVQD&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 212.25.15.128:22067: i/o timeout 2018-07-03 07:57:14 Could not connect to relay relay://195.219.226.6:443/?id=4PBE4M2-RARCLEN-F2P2OAN-JLRSGO3-R4XVGZK-LF4G3KW-3QQMFZK-DA6KNQD&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 195.219.226.6:443: i/o timeout 2018-07-03 07:57:24 Could not connect to relay relay://5.9.95.162:22067/?id=WQ72DYY-SILLQIS-JMA2FQC-ZMOA66M-XECI3PR-6RYLIZS-MSDINIL-ICFVWAW&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=some german dude: dial tcp 5.9.95.162:22067: i/o timeout 2018-07-03 07:57:34 Could not connect to relay relay://81.167.212.154:443/?id=6UXD2SS-7YJ4CCA-YP5CDVF-32PWZTL-R5OOOZF-YUIDERT-ICKL4SL-6Y5JNAV&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=E1des1vk: dial tcp 81.167.212.154:443: i/o timeout 2018-07-03 07:57:44 Could not connect to relay relay://163.172.132.71:587/?id=UDDV7DR-Y3I5FSN-6W2T2VW-S4JSRT6-QYFFA5E-6CXCGMJ-DJN4ATS-HAA46AF&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=zalupa: dial tcp 163.172.132.71:587: i/o timeout 2018-07-03 07:57:54 Could not connect to relay relay://185.86.148.197:22067/?id=SHJTVSC-52PEX7P-WAGIB7F-S34CR7S-I32WR4P-NDRILH4-PKS7MGV-LGSWXQJ&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 185.86.148.197:22067: i/o timeout 2018-07-03 07:57:55 Joined relay relay://51.255.75.9:22067 2018-07-03 09:08:46 Puller (folder “my_folder” (lmamp-ngzgf), file “folder1/folder2/folder3”): delete dir: directory is not empty

Do these logs help?

EDIT: I sshed into my raspberry and noticed that when trying to “ls” my hard-drive (which is where my synced syncthing folder is located) I get the following error:

ls: reading directory ‘.’: Input/output error

It sounds like that disk is broken, in which case Syncthing will struggle and results will be unpredictable.

@calmh There should be some fail-safes for these kind of situations (other than the .stversions). Is there something I should be doing on my end to safe-guard against these kind of things? Because often times I lose folders and I don’t even know. It’s pretty random on what it deletes.

There are a few failsafes in place, so just an IO error shouldn’t be considered a delete. But if the file system says “does not exist” that will be (correctly) interpreted as a delete, and if the file system is bad you may get all kinds of odd responses from the OS.

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