![filemass safe or not filemass safe or not](https://i.etsystatic.com/25382980/r/il/1e103e/3276854837/il_fullxfull.3276854837_9728.jpg)
In your case it looks like something happened to your filesystem so that the directory containing your folder started appearing empty to Syncthing. When the device gets plugged in again, Syncthing sees the folder marker again and continues operation. An example may be a folder on a removable device: if the device gets removed, the folder marker can no longer be seen, and that means no work should be done on this folder. This folder marker isn’t supposed to go anywhere, and if it disappears, Syncthing thinks something unexpected happened and stops. stfolder) at the root of a directory it works with. What happened here is you’ve overridden the safety measures built in to prevent exactly this kind of situation, and got shot in the foot as the result. Most of all of course I would like to understand what went wrong here, and how it could happen that Sync would start to delete all files on the source machine?
#Filemass safe or not how to#
However, the file names all contain a ~tilde and the modification (deletion?) date, so I first have to think about how to restore the original file names, and then restore the files back to the source PC… Thanks to File Versioning I seem to have a backup of the deleted files (knock on wood). stfolder from another synchronized folder over to the local “A” folder and restarted Sync.Ī minute later I accidentally saw on the remote (source) machine that Sync was about to mass-delete (thousands) of files from the source folder. stfolder file (or is it a folder?) was missing from the folder.
![filemass safe or not filemass safe or not](https://i.etsystatic.com/20513803/r/il/937133/2660673923/il_fullxfull.2660673923_f6wx.jpg)
What happened? On the local computer, Synctrayzor this morning reported “path exists, but folder marker missing” for my synchronized folder “A” for some unknown reason. The catastrophic case feared earlier has just hit me.