Stefan Bodewig wrote:
On Tue, 25 Jan 2005, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
On Tue, 25 Jan 2005, David Crossley <[EMAIL PROTECTED]> wrote:
Not sure what caused the sudden fill-up, but it is not me.
It seems as if the kaffe and public Gump workspaces lived on /home -
maybe one of them is generating a lot of logs ATM, I'll look into
it.
I couldn't find anything unusual. kaffe and public together take
almost the same amount of space as test and jdk1.5, so the disk space
cosumption we see is pretty much expected.
I managed to squeeze about one GByte out of home by moving the
installed packages and the jars generated by the public Gump instance
over to /usr. /home still is > 90% full, though.
A "quick" du -Hx on /home told me that we are spending almost all disk
space in /gump (~22G) where the only directories holding more than one
GByte are
4.3G ./gump/workspaces2/kaffe/workspace/cvs
7.3G ./gump/workspaces2/kaffe/workspace
6.2G ./gump/workspaces2/public/workspace/cvs
12G ./gump/workspaces2/public/workspace
so the two workspaces (checked out sources plus working copies for
builds) simply eat about 20G.
I don't know whether we stand any chance of getting more disk space
into brutus.
Apart from that, the only stuff we could share are the checked out
sources. And this only if we can ensure that no two CVS updates/SVN
updates on the same tree run in parallel, or an update in parallel
with a sync operation.
have you cleaned up the 'jars' directory?
--
Stefano.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
