Re: can't find certain doc

2002-10-23 Thread Nathan Kinkade
On Mon, Oct 21, 2002 at 02:49:46PM -0700, [EMAIL PROTECTED] wrote:
 I thought I saw a doc called something like 'what to do if your hard drive
 gets full'. I checked the docs
 the freebsd.org and couldn't find anything like that. Is there a doc out
 there some place that tells me
 what to do when the root partition fills up, for no apparent reason? This
 machine is strictly a web
 backup box and rarely is used for anything else, yet the root partition is
 at 104%.

Try:
# cd /
# du -h -d 1 -I usr

This should tell you how much space each file/dir is using in /,
excluding, the 'usr'.  Some  of  the other dirs are bound to be
mounted filesystems, but ignore those.  Exluding 'usr' just saves
a lot of time, as `du' doesn't have to calculate that beast of a
filesystem.

Nathan

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: can't find certain doc

2002-10-23 Thread Nathan Kinkade
On Wed, Oct 23, 2002 at 09:52:58AM -0700, [EMAIL PROTECTED] wrote:
 
 [EMAIL PROTECTED] wrote on 10/23/2002 09:02:41 AM:
 
  On Mon, Oct 21, 2002 at 02:49:46PM -0700, [EMAIL PROTECTED] wrote:
   I thought I saw a doc called something like 'what to do if your hard
 drive
   gets full'. I checked the docs
   the freebsd.org and couldn't find anything like that. Is there a doc
 out
   there some place that tells me
   what to do when the root partition fills up, for no apparent reason?
 This
   machine is strictly a web
   backup box and rarely is used for anything else, yet the root partition
 is
   at 104%.
 
  Try:
  # cd /
  # du -h -d 1 -I usr
 
  This should tell you how much space each file/dir is using in /,
  excluding, the 'usr'.  Some  of  the other dirs are bound to be
  mounted filesystems, but ignore those.  Exluding 'usr' just saves
  a lot of time, as `du' doesn't have to calculate that beast of a
  filesystem.
 
  Nathan
 
 That helps a lot, thanks, though I still haven't found any one particularly
 large file or directory. In /var/db/pkg is about 14megs, is it okay to
 clear
 that stuff? And in . is kernel and kernel.generic, do I need both of these?
 I have gotten the du down to 98% so far, on a 150meg / partition.

Can you sent the output of `df -h` and the output of `du -h -d 1 -I usr`
to the list?  Another common place to check is /tmp, unless, of course,
it's mounted on it's own filesystem - as it probably should be.
Technically, it's ok to get rid of kernel.GENERIC, but you probably
don't want to do this.  kernel.GENERIC may get you out of a bind
sometime if you have compiled your own kernel and for some reason it
won't boot.  However, if you haven't built your kernel and you never
plan to, and you are running the stock, generic kernel anyway you can
probably delete kernel.GENERIC without too much risk.

Nathan

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: can't find certain doc

2002-10-23 Thread chip . wiegand
[EMAIL PROTECTED] wrote on 10/23/2002 11:01:02 AM:

 On Wed, Oct 23, 2002 at 09:52:58AM -0700, [EMAIL PROTECTED] wrote:
 
  [EMAIL PROTECTED] wrote on 10/23/2002 09:02:41 AM:
 
   On Mon, Oct 21, 2002 at 02:49:46PM -0700, [EMAIL PROTECTED]
wrote:
I thought I saw a doc called something like 'what to do if your
hard
  drive
gets full'. I checked the docs
the freebsd.org and couldn't find anything like that. Is there a
doc
  out
there some place that tells me
what to do when the root partition fills up, for no apparent
reason?
  This
machine is strictly a web
backup box and rarely is used for anything else, yet the root
partition
  is
at 104%.
 
   Try:
   # cd /
   # du -h -d 1 -I usr
  
   This should tell you how much space each file/dir is using in /,
   excluding, the 'usr'.  Some  of  the other dirs are bound to be
   mounted filesystems, but ignore those.  Exluding 'usr' just saves
   a lot of time, as `du' doesn't have to calculate that beast of a
   filesystem.
 
   Nathan

  That helps a lot, thanks, though I still haven't found any one
particularly
  large file or directory. In /var/db/pkg is about 14megs, is it okay to
  clear
  that stuff? And in . is kernel and kernel.generic, do I need both of
these?
  I have gotten the du down to 98% so far, on a 150meg / partition.

 Can you sent the output of `df -h` and the output of `du -h -d 1 -I usr`
 to the list?

Output of df -h 

FilesystemSize   Used  Avail Capacity  Mounted on
/dev/ad0s1a   148M   132M   3.4M98%/
/dev/ad0s1e18G   3.7G13G23%/usr
linprocfs 4.0K   4.0K 0B   100%/usr/compat/linux/proc
procfs4.0K   4.0K 0B   100%/proc

Output of du -h -d 1 -I usr 

 70K  ./dev
2.1M  ./stand
2.8M  ./etc
2.0K  ./cdrom
 26K  ./proc
3.9M  ./bin
392K  ./boot
2.0K  ./mnt
5.1M  ./modules
212K  ./root
 11M  ./sbin
6.0K  ./tmp
 15M  ./var
2.0K  ./floppy
 48M  .


I cleaned up the mail for root and my own use account, both of which
made no appreciable differance in available space. Cleaned /tmp also.

--
Chip

  Another common place to check is /tmp, unless, of course,
 it's mounted on it's own filesystem - as it probably should be.
 Technically, it's ok to get rid of kernel.GENERIC, but you probably
 don't want to do this.  kernel.GENERIC may get you out of a bind
 sometime if you have compiled your own kernel and for some reason it
 won't boot.  However, if you haven't built your kernel and you never
 plan to, and you are running the stock, generic kernel anyway you can
 probably delete kernel.GENERIC without too much risk.

 Nathan

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: can't find certain doc

2002-10-23 Thread chip . wiegand

Jerry McAllister [EMAIL PROTECTED] wrote on 10/23/2002 10:44:38
AM:

 
  [EMAIL PROTECTED] wrote on 10/23/2002 09:02:41 AM:
 
   On Mon, Oct 21, 2002 at 02:49:46PM -0700, [EMAIL PROTECTED]
wrote:
I thought I saw a doc called something like 'what to do if your
hard
  drive
gets full'. I checked the docs
the freebsd.org and couldn't find anything like that. Is there a
doc
  out
there some place that tells me
what to do when the root partition fills up, for no apparent
reason?
  This is at 104%.
 
   Try:
   # cd /
   # du -h -d 1 -I usr
 
  That helps a lot, thanks, though I still haven't found any one
particularly
  large file or directory. In /var/db/pkg is about 14megs, is it okay to
  clear
  that stuff? And in . is kernel and kernel.generic, do I need both of
these?
  I have gotten the du down to 98% so far, on a 150meg / partition.

 or just:
cd /
du -sk *

 But, no matter what they try to tell you, 150 MB is awfully
 small for the root partition now days.

Thanks, I'll keep that in mind tonight when I set up a new box
at home. :)

--
Chip

 At that size you would
 have to manage stuff pretty tightly.   The thing you would have
 to do is have a nice pristine system and do the du.  Then when
 it starts to fill up, do a new du and compare to see what has
 been growing.   Do you have logs going somewhere besides root?
 What about root's Email?   Do you do any tinkering as root that
 might leave some files around.  All these things can use up that
 little space quickly.

 Anyway, about the only things you can do are to look for files to delete
 or directories to move to a different partition with a sym-link and/or
 to redo your partitions to make root a little bigger (250MB at least)
 either on that disk or get a new bigger disk and start clean.

 jerry

  --
  chip
 
   This should tell you how much space each file/dir is using in /,
   excluding, the 'usr'.  Some  of  the other dirs are bound to be
   mounted filesystems, but ignore those.  Exluding 'usr' just saves
   a lot of time, as `du' doesn't have to calculate that beast of a
   filesystem.
 
   Nathan
 
   To Unsubscribe: send mail to [EMAIL PROTECTED]
   with unsubscribe freebsd-questions in the body of the message
 
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message
 




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: can't find certain doc

2002-10-23 Thread Jerry McAllister
 
 [EMAIL PROTECTED] wrote on 10/23/2002 11:01:02 AM:
 I thought I saw a doc called something like 'what to do if your
 hard
   drive
 gets full'. I checked the docs
   is
 at 104%.
  
Try:
# cd /
# du -h -d 1 -I usr
   
This should tell you how much space each file/dir is using in /,
excluding, the 'usr'.  Some  of  the other dirs are bound to be
mounted filesystems, but ignore those.  Exluding 'usr' just saves
a lot of time, as `du' doesn't have to calculate that beast of a
filesystem.
  
Nathan
 
   That helps a lot, thanks, though I still haven't found any one
 particularly
   large file or directory. In /var/db/pkg is about 14megs, is it okay to
   clear
   that stuff? And in . is kernel and kernel.generic, do I need both of
 these?
   I have gotten the du down to 98% so far, on a 150meg / partition.
 
  Can you sent the output of `df -h` and the output of `du -h -d 1 -I usr`
  to the list?
 
 Output of df -h 
 
 FilesystemSize   Used  Avail Capacity  Mounted on
 /dev/ad0s1a   148M   132M   3.4M98%/
 /dev/ad0s1e18G   3.7G13G23%/usr
 linprocfs 4.0K   4.0K 0B   100%/usr/compat/linux/proc
 procfs4.0K   4.0K 0B   100%/proc
 
 Output of du -h -d 1 -I usr 
 
  70K  ./dev
 2.1M  ./stand
 2.8M  ./etc
 2.0K  ./cdrom
  26K  ./proc
 3.9M  ./bin
 392K  ./boot
 2.0K  ./mnt
 5.1M  ./modules
 212K  ./root
  11M  ./sbin
 6.0K  ./tmp
  15M  ./var
 2.0K  ./floppy
  48M  .
 
 
 I cleaned up the mail for root and my own use account, both of which
 made no appreciable differance in available space. Cleaned /tmp also.

How about /var?   If it has not alrady been done, I would move
at least /var/spool and /var/logs to your big partition (/usr here)
and make sym links to them   Also, I always make /tmp a separate
partition to keep accidents from clobbering /.

jerry

 
 --
 Chip
 
   Another common place to check is /tmp, unless, of course,
  it's mounted on it's own filesystem - as it probably should be.
  Technically, it's ok to get rid of kernel.GENERIC, but you probably
  don't want to do this.  kernel.GENERIC may get you out of a bind
  sometime if you have compiled your own kernel and for some reason it
  won't boot.  However, if you haven't built your kernel and you never
  plan to, and you are running the stock, generic kernel anyway you can
  probably delete kernel.GENERIC without too much risk.
 
  Nathan
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: can't find certain doc

2002-10-23 Thread Giorgos Keramidas
On 2002-10-23 10:30, [EMAIL PROTECTED] wrote:
 I understand that, it's not the whole hard drive, just the root
 partition.  There's 15gigs available on the /usr partition.

You can move /var into /usr and symlink /var - /usr/var.  Bring the
system down to single user mode while doing that, to avoid nasty
surprises from daemons that are already using files under /var.

Giorgos.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: can't find certain doc

2002-10-23 Thread Gary W. Swearingen
  But, no matter what they try to tell you, 150 MB is awfully
  small for the root partition now days.

If it's small now, it's been small for many years.  It's not
unreasonable to consider it small, but lots of people don't mind the
little trouble it takes to keep it well under that size.  That's mostly
taken care of by pointing /var, /tmp, /usr, and /home elsewhere.  I
think the argument is that the less you use /, the less likely you are
to mess it up so you can't boot even into single user mode.

Another way to find out what's filling /:

du -xd 1 /## Just dir trees on / device
find / ! -type d -maxdepth 1 -ls  ## Just non-dirs in / dir

 Thanks, I'll keep that in mind tonight when I set up a new box
 at home. :)

You might want to ensure that /var and /tmp point to real directories
even when only / is mounted by pointing them at directories on / that
get hidden after you mount things.  Different topic: I like to point
/tmp to something under /var and then worry only about /var.  (I keep 
my small home under /var too.)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: can't find certain doc

2002-10-23 Thread Lowell Gilbert
Jerry McAllister [EMAIL PROTECTED] writes:

 But, no matter what they try to tell you, 150 MB is awfully
 small for the root partition now days.

Or, looking at it a different way, 150 MB *used* to be
really small, but is now quite big, because /var and /tmp
should probably not be on it.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: can't find certain doc

2002-10-23 Thread Chip Wiegand
Lowell Gilbert wrote this stuff on 23 Oct 2002 23:42:45 -0400:

 Jerry McAllister [EMAIL PROTECTED] writes:
 
  But, no matter what they try to tell you, 150 MB is awfully
  small for the root partition now days.
 
 Or, looking at it a different way, 150 MB *used* to be
 really small, but is now quite big, because /var and /tmp
 should probably not be on it.
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 

What's most interesting, I find, is that this machine get very little
use, it's primarily a backup of a web site on an isp's server, and
occasionally I'll copy files I'm working on to it via windoze network
neighborhood. I rarely actually log into the box, then only as user, so
even more rarely use the su account.

I have always symlinked /var and /tmp to /usr/var and /usr/tmp on my
setups.

--
Chip Wiegand
computer Services
Simrad, Inc

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message