[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 ---- Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 148M 132M 3.4M 98% / /dev/ad0s1e 18G 3.7G 13G 23% /usr linprocfs 4.0K 4.0K 0B 100% /usr/compat/linux/proc procfs 4.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
