We have triggered a re-sync for some users on our experimental build (2.11 series). We discovered an issue in an earlier version of the 2.11 series that would cause the local database state to be incorrect. This is fixed by a re-sync so we have issued it to the affected users.

A re-sync will require re-scanning and re-indexing all of the files in your Dropbox, so it can take a while for users with very large Dropboxes (many hours to days for the largest Dropboxes). During the course of the re-sync you may receive notifications saying you joined your existing shared folders (this is normal). Please be patient and let the process complete (unlinking and relinking will just restart the process from scratch). It might be worth running this overnight so that it does not hog the resources on your machine.

We are working hard on improving the re-sync experience and performance. We're sorry we had to issue the re-sync to some of you, and we thank you for helping us test our beta builds!

Let us know if you run into any issues and we can help debug further.