Messages

Thanks for the info Greg.

I've worked with my free 2GB Dropbox test account, first reducing the containing sparsebundle on my system to 1GB capacity, then trying to add more than 1GB to induce the Dropbox client error, then re-sizing the sparesbundle to 10GB and subsequently successfully adding more than 1GB to Dropbox.

I will get back to my client and see if I can't straighten out whatever is going with his system. Will let you and the forum know how it goes.

I've set up a customer with Dropbox 0.7.110 and Espionage 2.6.1. 50GB Dropbox account; Mac running 10.6.3 with over 160GB free on the disk.

I set up Espionage and moved the local Dropbox folder into the encrypted Espionage folder, per the recent guide: http://www.taoeffect.com/blog/2009/12/u ... h-dropbox/

Everything was fine at first, but he got error messages from Dropbox after hitting about 10GB of utilizaton. The errors report that there is not enough "free space" on the local system, e.g.: "The item "PHI" can't be copied because there isn't enough free space."

At first I assumed that this was due to the default Minimum Image Capacity in Advanced prefs in Espionage, which was at the 10240MB default. We moved Dropbox out of Espionage temporarily, deleted the existing vault, reset the MIC to 51300MB (50GB plus 100MB), then re-created a new vault folder and moved Dropbox into it.

Still getting the free space error on the Dropbox client.

What can be done about this? Is there some sort of three-way problem whereby OS X is not reporting the actual Espionage sparsebundle capacity to Dropbox? I've been investigating this guide on my own 10.6.3 Mac,

viewtopic.php?f=3&t=83

but it's not clear to me if that procedure is applicable here. Also, how do I actually tell via the terminal what the capacity of the Espionage sparsebundle is? "ls -al" shows the actual sparsebundle for my Espionage folder as 204 bytes, and the entire vault folder as 272 bytes, but it contains a Dropbox that is using 151MB on the Dropbox system.