Bug report: Cloudsync, Dropbox and encrypted volumes - data loss?

[korev]

I setup my F8 SSD Plus running TOS 6 with an encrypted volume onto which I synchronised Dropbox. I turned the NAS off as I was away for the Christmas holidays and turned it back on upon my return. Shortly after this I noticed that quite a few files were being deleted from Dropbox which in turn were removed from my laptop. As soon as I noticed this I turned the NAS off.

The timing of this coincided with me turning the NAS on. I wonder if the Dropbox client on the NAS looked for files, couldn't see any (I'd not had a chance to enter the decryption keys) and therefore flagged them as deleted to Dropbox.

I believe I'm running the latest versions of both TOS and the Cloudsync client; however, I'm obviously not about to turn the NAS on and risk losing my data.

Luckily I was able to use Dropbox's functionality to roll back the deletion and restore my files.

[TMLila]

I setup my F8 SSD Plus running TOS 6 with an encrypted volume onto which I synchronised Dropbox. I turned the NAS off as I was away for the Christmas holidays and turned it back on upon my return. Shortly after this I noticed that quite a few files were being deleted from Dropbox which in turn were removed from my laptop. As soon as I noticed this I turned the NAS off.

The timing of this coincided with me turning the NAS on. I wonder if the Dropbox client on the NAS looked for files, couldn't see any (I'd not had a chance to enter the decryption keys) and therefore flagged them as deleted to Dropbox.

I believe I'm running the latest versions of both TOS and the Cloudsync client; however, I'm obviously not about to turn the NAS on and risk losing my data.

Luckily I was able to use Dropbox's functionality to roll back the deletion and restore my files.

Hello! Thank you for your feedback! I have carefully documented this issue in detail and submitted it to our project team. The technical team will verify the issue in a lab environment. If it is confirmed as a software defect (Bug), the fix will be released in subsequent version updates. Thank you for your support and patience!