4 ms·

Affected me today by screwing up Backblaze's .bzvol folder and disassociating the volume from the backup service. Luckily it didn't delete anything vital, and

Affected me today by screwing up Backblaze's .bzvol folder and disassociating the volume from the backup service. Luckily it didn't delete anything vital, and the temporary fix is to just make a /.aaaaa folder for now. But what on Earth did Adobe do? How does something like that even happen? Here are two videos showing the problem: https://www.youtube.com/watch?v=0xKlFO3_j5E https://www.youtube.com/watch?v=0xKlFO3_j5E https://www.youtube.com/watch?v=XHrhygLKtLQ https://www.youtube.com/watch?v=XHrhygLKtLQ

atYevP 11y ago
Yev from Backblaze here -> sorry! It took us all day to figure out what the hell was going on. Kept getting folks writing in, when nothing had changed on our end. Our Mac dev probably left a dent in his wall from trying to figure it out. We finally narrowed it down to the ACC update. Then realized that WE were affected more than most apps simply because .bzvol starts with a "B" and so a bunch of our users were affected. Likely if a user had a hidden folder with data in it named anything /.0-/.a that folder's data could have been removed as well (we tested this). So hopefully they had a backup/hidden folders are rare and few were affected.