On Sun, Dec 27, 2009 at 10:34 AM, SmallSister development <smallsis...@xs4all.nl> wrote: > Evan Daniel wrote: >> Persistent-temp is not part of the datastore, and is not expected to >> stay within the datastore size limit. It's used to hold data from >> partially completed downloads. In theory, it will only grow to be >> slightly larger than your total queue size. However, there appear to >> be some bugs that make it leak space slowly. If it grows beyond your >> total queue size rapidly, though, that's not something I've seen. > > I can live with some additional disk-space use for "downloaded files in > transit"; if it cleans up after the downloads are complete. (I planned a > few gigs for downloads I configured Freenet.) Yet, presistent-temp grew > over the weeks to achieve 11 GB... with several wrapper-induced > shutdowns of Freenet. (The db4o implementation for downloads can get > pretty unresponsive at times.) > > But with 17GB datastore (15 GB configured) PLUS 11GB in persistent-temp > Freenet eats the best part of a 30 GB partition... Reclaiming ~9GB in > unused temp files would make quite a difference. >
The workaround for persistent-temp is to shut down the node, then delete node.db4o and persistent-temp-*/ and restart the node. Warning, this will remove all in-progress uploads/downloads, so let those complete first. Evan Daniel _______________________________________________ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
