Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Oct 2004 11:09:20 -0400
From:      Bill Moran <wmoran@potentialtech.com>
To:        bill <william@TechServSys.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: /usr is growing and growing
Message-ID:  <20041005110920.50593e29.wmoran@potentialtech.com>
In-Reply-To: <4162B73C.1060908@TechServSys.com>
References:  <4162B73C.1060908@TechServSys.com>

next in thread | previous in thread | raw e-mail | index | archive | help
bill <william@TechServSys.com> wrote:

> uname -a:
> 
> FreeBSD serve.TechServSys.com 4.6.2-RELEASE FreeBSD 4.6.2-RELEASE #0: Wed Aug 14 21:23:26 GMT 2002     murray@builder.freebsdmall.com:/usr/src/sys/compile/GENERIC  i386
> 
> This box is a web server only.  The web files are on their own filesystem
> which is at 8% utilization.
> 
> I have watched the /usr file system grow from about 69% utilization to
> 85% utilization over 2 years and can not figure out what is taking the
> space.  Doing a find . -mtime -2 -print yields no files modified.
> A find . -size +2000 -print yields only expected files.
> 
> Would someone be kind enough to give me suggestions as to what is using
> up the space and/or how to find out ?

[Please wrap you lines around 72 chars:
 see http://www.lemis.com/questions.html ]

I don't have a guess as to the specific problem.  I assume you've checked
to see where your web server is logging to, and ensured that you're
managing it.

When I have problems like this, I start with:
du -hd1 /usr

Then I look at directory sizes, and possibly narrow it down more:
du -hd1 /usr/local

... etc. ... until I've located the large files on the filesystem. I
can then usually determine what is causing those large files.

If I had to make a guess ... I would suspect that something is logging
to /usr somewhere, without you realizing it.  But I can only guess.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041005110920.50593e29.wmoran>