We received several reports from users who used a Dropbox feature called Selective Sync and couldn’t locate certain files they’d saved in Dropbox.
When we took a closer look, we discovered that older versions of the Dropbox client had introduced an issue affecting a small number of users whose Dropbox application shut down or restarted while users were applying Selective Sync settings.
In light of all of this, we've taken the following steps to ensure the Selective Sync bug won’t affect anyone else going forward:
1) we've patched our desktop client so this issue doesn't exist in Dropbox anymore;
2) we've made sure all our users are running an updated version of the Dropbox client; and
3) we've retired all affected versions of the Dropbox client so no one can use them.
We've also put additional testing in place to prevent this from happening in the future.
We’re very sorry about this issue and the trouble it might have caused. We’ll keep doing our best to ensure our users' data is always safe and available to them.
We received several reports from users who used a Dropbox feature called Selective Sync and couldn’t locate certain files they’d saved in Dropbox.
When we took a closer look, we discovered that older versions of the Dropbox client had introduced an issue affecting a small number of users whose Dropbox application shut down or restarted while users were applying Selective Sync settings.
In light of all of this, we've taken the following steps to ensure the Selective Sync bug won’t affect anyone else going forward:
1) we've patched our desktop client so this issue doesn't exist in Dropbox anymore;
2) we've made sure all our users are running an updated version of the Dropbox client; and
3) we've retired all affected versions of the Dropbox client so no one can use them.
We've also put additional testing in place to prevent this from happening in the future.
We’re very sorry about this issue and the trouble it might have caused. We’ll keep doing our best to ensure our users' data is always safe and available to them.
I was affected by this, but I realized it at the time.
I have an older laptop that I turned on. It was a work laptop a few years ago, linked to my dropbox account, etc. Since then I had added a bunch of things like a bunch of git repos to a folder included in dropbox.
I turned on that laptop and Dropbox started using 100% cpu after a few minutes. Then the fan kicked on and it was annoyingly loud so I looked at dropbox and saw it was chugging along in the repos directory. I went ahead and clicked on selective sync, unchecked repos, and left it alone for about 5 minutes.
It was still 100% cpu, so I killed the dropbox task and restarted it.
Minutes later, on another machine, I went to fetch from one of the repos and it had a gnarly error. So I went about investigating.
I found my way to the dropbox events tab (on the website - the desktop client doesn't have this feature) and saw an event where dropbox decided to delete 7,800 files.
I submitted a support request, but before they responded I had figured out it was (mostly) in the repos directory, which I fixed by simply deleting the repos and pulling from one of my servers.
Anyways. There's my real world run in with this bug.
This is exactly why sync is not a commodity. Dropbox is the very best at what they do, and even they have bugs. So when someone offers to sync your files for less, ask why.
The sync heavy lifting in Dropbox is handled by librsync, or at least was at one point. librsync is very mature open source software, and this bug pertains to a particular interaction between the Dropbox GUI and a feature (selective sync) which they have somewhat tacked on to the core library. Long story short, you don't necessarily have to be Dropbox or employ a couple hundred software engineers to get inotify + rsync working well.
> This is exactly why sync is not a commodity. Dropbox is the very best at what they do,
The very best? I use OneDrive across all of my Windows machines and I don't even notice it exists; never had any problems. I just access all my files everywhere. If you buy a windows phone you even get a decent amount of space for free (15GB). (Though I subscribe to Office 365 so I have virtually unlimited space.)
I thought there were many robust open source solutions out there and what made dropbox the winner was not that it is able to reliably sync, but that they made it easy to install and sync.
I aggressively use selective sync, and have since as long as I can remember yet I haven't got an email like this, so it may only affect specific users.
It appears the circumstance is more specific than simply using selective sync.
> This problem occurred when the Dropbox desktop application shut down or restarted while users were applying Selective Sync settings.
So, you must be in the midst of applying selective sync settings while the app shuts down or restarts. Although I'm not sure what they mean when they say, "while users were applying selective sync settings." I'm not sure if this means:
A) Changes made in the selection dialog box, but not committed (by clicking OK).
or
B) Changes committed, but still syncing.
The former is an edge case, the later, not so much.
Dropbox should have understood that people are using it as a backup service. I mean carousel and other use cases sort of ebcourage and imply this. With that in mind, it baffling they didn't have any proper backups for user data.
It is a shame that they don't offer the unlimited packrat option anymore. It's still not backup, but at the very least people would be able to recover files in such cases.
Also, if I understand correctly, Google Drive has a better policy here: removed files are just placed in the trash until you remove them from the trash. Of course, trash takes space up as well, but it protects better against such cases.
I guess Dropbox is trying to maximize its profits with its 'remove after 30 days' policy.
I use packrat - so the files they suggest that I might have had deleted were recoverable (though none of them were an error).
If dropbox kept backups like you're suggesting, people would be complaining about how you can't delete damning files from them and that law enforcement was abusing this.
I disagree. A local tape NAS is also not a good backup, (god forbid) your house can burn down. A remote service like Backblaze is also not a good backup, they could go bankrupt or a software error could corrupt all your backups.
A good backup policy uses a mixture of onsite and offsite, and Dropbox can be a (convenient) part of that. E.g., I store (non-sensitive) files in Dropbox, which gives me a certain period of undelete possibilities. My Dropbox folder is backed up on a local time machine backup. Critical parts of my Dropbox are also backed up using tarsnap, etc.
A good backup policy diversifies, and Dropbox can be part of that.
It can be a backup client, as long it's not the only one. I use OneDrive + a local NAS as my backup. Both have advantages and disadvantages, but having at least one copy locally and one copy in the cloud is quite safe. Obviously these two must not be synced in realtime (because if the sync software screws something up, then you might lose everything) -- so I just keep everything on OneDrive, and every couple of weeks manually copy the files (this is still not 100% safe because of possible file corruption issues, but it's OK for me).
We provide a self hosted sync offering for businesses. It is currently used by close to 1000 businesses. It took us almost 18 months from our launch to get the sync right. There are simply too many edge cases and the development team needs to closely work with the customers to identify and fix it. Even then our complexity is much less than dropbox. The largest customer of ours have 10000 users.
Short story: if you plan to develop a sync product from scratch, be prepared to spend at least 2 years or hire core developers from Dropbox sync team. Eve now dropbox has issues with handling large number of small files. Try to stuff 200000 to 300000 files and see how it works.
I was notified of the potential data loss and checked my data on the 'personalized web page.' Of the 12,000 files that may have been affected, I found only a subfolder of a few dozen photos that may've been removed.
The problem is that when I clicked 'restore all' from within the subfolder, Dropbox restored all 12,000 files rather than just the files within the folder.
Note to DB's UX team: when you place a Restore All checkbox above the lefthand file selection column, it means 'select and restore all files on the page', not 'lift the roof off my house and dump in all the shit I spent months decluttering.'
Ha, dropbox deleted my files the other day presumably due to this bug. I ranted on Twitter and they came back with the dropbox client can't delete files. Hmmmm. Seems I was correct :-/
I have all my digital life on dropbox, a few hundred gig.
One of my greatest fears is that thousands of files might disappear without me noticing for years.
I use selective sync and twice I was looking for something that has disappeared and I have to restore it. I assumed maybe my wife accidentally deleted some files, but maybe it was dropbox?
Perhaps you can have a cron job run against your local dropbox folder(s) and do an "md5deep" reporting only differences (or sha1deep or whatever, perhaps test which uses least resources, maybe nice it heavily too). Then you could have the output report saved to a folder (not a dropbox one!). Perhaps add another job to email/alert you if the "count" of lines in the report is greater than a certain number? Crude, for sure.
Don't put all your eggs in one basket. Keep all the same data stored on another service, as well as on a physical backup that you keep yourself. If it's really important data you might keep a copy in a safe deposit box.
This manifested for me as a large number of "conflicted copies" everywhere inside my main visual studio solution. Thankfully, source control saved the day... But I was really annoyed at Dropbox for a little while.
As founder of cloudHQ, I have to jump into this.
Software products will have bugs. And people will make mistakes. We are all human.
So even if you store data in Dropbox - it is smart to have one extra copy in some other cloud storage. Like Google Drive. Or Box. Or Egnyte. So if data is deleted in Dropbox (accidentally, maliciously, or due to a bug) you can restore it from other cloud.
I stopped using Dropbox because of this. I booted my system up one day and a ton of my files were deleted (locally). Luckily, this didn't affect the sync on my other systems.
[+] [-] ghuntley|11 years ago|reply
[+] [-] Ma8ee|11 years ago|reply
We received several reports from users who used a Dropbox feature called Selective Sync and couldn’t locate certain files they’d saved in Dropbox.
When we took a closer look, we discovered that older versions of the Dropbox client had introduced an issue affecting a small number of users whose Dropbox application shut down or restarted while users were applying Selective Sync settings.
In light of all of this, we've taken the following steps to ensure the Selective Sync bug won’t affect anyone else going forward:
1) we've patched our desktop client so this issue doesn't exist in Dropbox anymore; 2) we've made sure all our users are running an updated version of the Dropbox client; and 3) we've retired all affected versions of the Dropbox client so no one can use them.
We've also put additional testing in place to prevent this from happening in the future.
We’re very sorry about this issue and the trouble it might have caused. We’ll keep doing our best to ensure our users' data is always safe and available to them.
[+] [-] NDizzle|11 years ago|reply
I have an older laptop that I turned on. It was a work laptop a few years ago, linked to my dropbox account, etc. Since then I had added a bunch of things like a bunch of git repos to a folder included in dropbox.
I turned on that laptop and Dropbox started using 100% cpu after a few minutes. Then the fan kicked on and it was annoyingly loud so I looked at dropbox and saw it was chugging along in the repos directory. I went ahead and clicked on selective sync, unchecked repos, and left it alone for about 5 minutes.
It was still 100% cpu, so I killed the dropbox task and restarted it.
Minutes later, on another machine, I went to fetch from one of the repos and it had a gnarly error. So I went about investigating.
I found my way to the dropbox events tab (on the website - the desktop client doesn't have this feature) and saw an event where dropbox decided to delete 7,800 files.
I submitted a support request, but before they responded I had figured out it was (mostly) in the repos directory, which I fixed by simply deleting the repos and pulling from one of my servers.
Anyways. There's my real world run in with this bug.
[+] [-] phren0logy|11 years ago|reply
[+] [-] hyperbovine|11 years ago|reply
[+] [-] zvrba|11 years ago|reply
The very best? I use OneDrive across all of my Windows machines and I don't even notice it exists; never had any problems. I just access all my files everywhere. If you buy a windows phone you even get a decent amount of space for free (15GB). (Though I subscribe to Office 365 so I have virtually unlimited space.)
[+] [-] wodenokoto|11 years ago|reply
[+] [-] darrenkopp|11 years ago|reply
[+] [-] bradleyland|11 years ago|reply
> This problem occurred when the Dropbox desktop application shut down or restarted while users were applying Selective Sync settings.
So, you must be in the midst of applying selective sync settings while the app shuts down or restarts. Although I'm not sure what they mean when they say, "while users were applying selective sync settings." I'm not sure if this means:
A) Changes made in the selection dialog box, but not committed (by clicking OK).
or
B) Changes committed, but still syncing.
The former is an edge case, the later, not so much.
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] ghuntley|11 years ago|reply
[+] [-] general_failure|11 years ago|reply
[+] [-] microtonal|11 years ago|reply
Also, if I understand correctly, Google Drive has a better policy here: removed files are just placed in the trash until you remove them from the trash. Of course, trash takes space up as well, but it protects better against such cases.
I guess Dropbox is trying to maximize its profits with its 'remove after 30 days' policy.
[+] [-] mayneack|11 years ago|reply
If dropbox kept backups like you're suggesting, people would be complaining about how you can't delete damning files from them and that law enforcement was abusing this.
[+] [-] Lazare|11 years ago|reply
[+] [-] microtonal|11 years ago|reply
A good backup policy uses a mixture of onsite and offsite, and Dropbox can be a (convenient) part of that. E.g., I store (non-sensitive) files in Dropbox, which gives me a certain period of undelete possibilities. My Dropbox folder is backed up on a local time machine backup. Critical parts of my Dropbox are also backed up using tarsnap, etc.
A good backup policy diversifies, and Dropbox can be part of that.
[+] [-] Dylan16807|11 years ago|reply
If you want to be picky you shouldn't rely on backups unless you have multiple independent backup systems, at least one offsite, at least one offline.
[+] [-] sz4kerto|11 years ago|reply
[+] [-] naiyt|11 years ago|reply
[+] [-] sanyo|11 years ago|reply
Short story: if you plan to develop a sync product from scratch, be prepared to spend at least 2 years or hire core developers from Dropbox sync team. Eve now dropbox has issues with handling large number of small files. Try to stuff 200000 to 300000 files and see how it works.
[+] [-] chdir|11 years ago|reply
https://www.dropbox.com/release_notes
[+] [-] waverunner|11 years ago|reply
The problem is that when I clicked 'restore all' from within the subfolder, Dropbox restored all 12,000 files rather than just the files within the folder.
Note to DB's UX team: when you place a Restore All checkbox above the lefthand file selection column, it means 'select and restore all files on the page', not 'lift the roof off my house and dump in all the shit I spent months decluttering.'
[+] [-] mayneack|11 years ago|reply
[+] [-] andy_ppp|11 years ago|reply
[+] [-] kwijibob|11 years ago|reply
One of my greatest fears is that thousands of files might disappear without me noticing for years.
I use selective sync and twice I was looking for something that has disappeared and I have to restore it. I assumed maybe my wife accidentally deleted some files, but maybe it was dropbox?
What is the solution to this anxiety?
[+] [-] pbhjpbhj|11 years ago|reply
[+] [-] jeffpetes|11 years ago|reply
[+] [-] h43k3r|11 years ago|reply
[+] [-] dmdeller|11 years ago|reply
[+] [-] andrea_s|11 years ago|reply
[+] [-] sdizdar|11 years ago|reply
So even if you store data in Dropbox - it is smart to have one extra copy in some other cloud storage. Like Google Drive. Or Box. Or Egnyte. So if data is deleted in Dropbox (accidentally, maliciously, or due to a bug) you can restore it from other cloud.
Of course, cloudHQ is the system which can do that: http://chq.io/hnsc
[+] [-] paulhauggis|11 years ago|reply
[+] [-] copper_rose|11 years ago|reply
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] nintendo1889|11 years ago|reply
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] coldtea|11 years ago|reply
http://www.digitaltrends.com/computing/google-confirms-missi...
And privacy/government implications wise, Google is hardly any better than Rice...