Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Dec 2001 15:55:48 -0800 (PST)
From:      Annelise Anderson <andrsn@andrsn.stanford.edu>
To:        Tom Kersten <tomkersten98@yahoo.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Question on Resizing /
Message-ID:  <Pine.BSF.4.10.10112031540200.59936-100000@andrsn.stanford.edu>
In-Reply-To: <20011203220058.85392.qmail@web10008.mail.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 3 Dec 2001, Tom Kersten wrote:

> Everyone,
> 
> Here is the information you asked for. I have /var &
> /tmp symlinked to their user counterparts. I had used
> X as root a couple times before...not knowing any
> better...but have since stopped the habit and I think
> I have removed all of the files related to it in the
> /root directory. My / slice is approximately 45mb., is
> this enough room? I have been close to 100% twice
> now...once because of using X as root, and now I am
> close again....any ideas on how I can fix it, or do I
> need to do a clean install?? Any advice is much
> appreciated. Here is the outputs and contents of the
> system as of now:
> 
...
> 
> thomas> df
> Filesystem  1K-blocks     Used    Avail Capacity 
> Mounted on
> /dev/ad0s4a     44623    39062     1992    95%    /
> /dev/ad0s4e  34880356  5057536 27032392    16%    /usr
> /dev/ad0s2    4177376  2071424  2105952    50%   
> /win1
> /dev/ad0s3   11507352  5902976  5604376    51%   
> /win2
> procfs              4        4        0   100%   
> /proc
> 
You can run swapinfo to see how large your swap partition is.  If
it's larger than it needs to be, and is continguous to your /,
that's an interesting solution.

But 40MB is too small for / (even assuming /var is separate or
successfully symlinked elsewhere).

On 4.x--and not the most recent--I have approximately this:

/sbin	 10MB
/bin	  4MB
/etc	  1MB
/stand	  1MB
/modules  4MB

Plus I've got the usual three kernels at, say, 4MB each--
kernel.GENERIC, kernel, kernel.old.  A new kernel build would
back up the /modules directory. That's close to 40MB right
there and no room to play.

You could look around the directories to see if you downloaded
something to /bin or /sbin or /etc in error; but basically
you want all the files in these directories, and you don't
want them in /usr, unavailable on boot.

You might delete old kernels or save them in /usr somewhere;
you can probably delete some modules you don't need; but this
is just a stop-gap measure.  You'd have to build new kernels
without building modules to prevent the / partition filling
up again. / should be 100MB or so.

The recognition that you need to reinstall (or use growfs on
the / file system) is an opportunity to experiment.  While you're
at it, give /var 80MB or even 100 in a separate partition, too.

	Annelise
-- 
Annelise Anderson
Author of: 		 FreeBSD: An Open-Source Operating System for Your PC
Available from:	 mall.daemonnews.org and amazon.com
Book Website:    http://www.bittreepress.com/FreeBSD/introbook/	




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10112031540200.59936-100000>