Preamble: recently I had an issue with .gddoc and .gdsheets file disappearing I thought I would let the client sync again.
I wanted to switch to headless since my desktop environment is minimal and I do not need a GUI, so I quitted insync desktop, renamed my Drive folder, installed insync-headless, configured it and started the synchronization.
After it completed I figured that headless has a differente licensing scheme and would expire in a few days. I quitted insync-headless, moved the Drive folder again and restarted insync desktop.
At this point I also started my laptop, running its insync desktop instance as it had been for several months.
At some point I heard the laptop fans spinning at high throttle, I checked processes and an insync thread was stuck at 100% CPU usage. I quit insync and shut down the laptop.
This morning the main computer insync was stuck at 100% well, turns out since the renaming of ~/Drive I had not created the folder and insync was stuck on an error for the missing folder (have you met os.makedirs?). Once I created the folder and restarted insync desktop I waited for the files on GDrive to be synced back to the main computer.
After a few hours the folder was 0 B in size.
I opened Google Drive web interface and found a completely empty My Drive.
From what I can tell the lack of the folder was recognized by the client as if I had deleted all the files.
I understand this could be convenient on the development side, rather than, say, check inodes or something more factual.
If I did not have a backup I would have been much more worried.
The data were found in Google Drive bin, to be clear, still I find Insync to be quite unreliable in terms of syncing multiple computers for my needs.
I am honestly looking for alternatives, hopefully in open source. At least when something breaks I do not need to send out a log blob to be inspected, losing control over my (meta)data.
