I think this would be a bummer, because there should be a fairly simple technical solution to this, and they are:ĭropbox either has OR SHOULD HAVE a setting for the maximum size of the cache, the way browsers do. Do not keep frequently updated logs on Dropbox. I just cleared it, and my understanding is there are no consequences other than resync, but this is unsustainable.ĭropbox is not suitable for this use case. My total local Dropbox folder has 150 GB of which 50 GB is the cache! I have the same issue with the exact same cause (took a while to figure out too): a log file inside a Dropbox folder that is actually not that big (several MB), but it does update every minute with a couple of hundred bytes. Unfortunately can't respond to your inquiry due to a large volume of support While we'd love to answer every question we get, we
Update: I tried opening a Dropbox support request, only to get an e-mail reply stating: "Thanks for writing in. Is there some way to do this? My searches so far have turned up empty. So from the standpoint of performance, it is kinda undesirable that it keep creating duplicates of this large file for every tiny addition of a few bytes to the file.ĭisk space is rather tight on this machine, so I would rather simply have Dropbox limit how much caching it does. In addition, it appears that the reason Dropbox is running out of space so fast is that I have a single large log file (on the order of half a gigabyte) which is append-only, but Dropbox is creating a new cached copy of the entire old version every time a change is made. (Update: It appears that deleting the files in a low disk condition results in Dropbox starting to sync again without restarting, but I am not sure if there are any undesirable side-effects to this, everywhere I have read about the cache says to stop Dropbox during the delete and restart it afterwards.) (For instance, the disk could fill up before the script runs.) This also seems to limit my options for automatically clearing the cache, although having to create a periodic task to clean the Dropbox folder seems kludgy and error prone. I have read that it is possible to clear the cache, but this is a pain as this machine is running OS X and there is no command line interface, meaning that I have to VNC into the machine simply to restart Dropbox. This is a problem because the machine Dropbox is installed on is headless (or nearly so) and therefore the only indication that something is wrong is suddenly data that should be available on the machine isn't. I am having an issue with the Dropbox cache, whereby periodically I find that a particular machine I am syncing to with Dropbox has run out of disk space and the Dropbox cache is the culprit.
0 kommentar(er)
