Re: compiling error - /usr : filesystem full

2007-02-08 Thread Don Munyak

Here's some additional Information I have been able to find. The
narrative is just to further explain what I was doing.
-
I was in the process of rebuilding a new kernel for one of my laptops.
I did the whole cvsup_without-gui. I created a new kernel called
LAPTOP and commented all unnecessary drivers and options.

When I ran make buildkernel KERNCONF=LAPTOP, the process eventually
died with an error. I neglected to write down the exact error, but it
was something like

{objcopy) /usr : filesystem full

As you can see /usr is choking. I have not turned off the laptop.
Based on the information below, what can I delete to free up some
space. I use the word delete in broad terms. Much like the windows
world where you should 'uninstall' as opposed to simply deleting a
folder...I am not sure what to do...ie how to free up space.

The only thing I can think of is to simply # rm /usr/ports ... for
lack of a better example.

# du -ak /usr |sort -nr |  /tmp/file2.txt
This file had 24,000 lines so I deleted much of the file.

Your thoughts/suggestions will be much appreciated.



### output from running # df -m  /tmp/file1.txt
### where -m is MB
Filesystem  1M-blocks Used Avail Capacity  Mounted on
/dev/ad0s1a   495   55   40012%/
devfs   00 0   100%/dev
/dev/ad0s1e   495   10   445 2%/tmp
/dev/ad0s1f  2300 2286  -170   108%/usr
/dev/ad0s1d  1098   58   952 6%/var
devfs   00 0   100%/var/named/dev


### output from running # du -ak /usr |sort -nr |  /tmp/file2.txt
### where -a is 'display entry for each file in file hierarchy
### where -k is 'display block count in kilobyte'
2341378/usr
636728/usr/obj
636726/usr/obj/usr
636724/usr/obj/usr/src
428576/usr/src
402064/usr/ports
289070/usr/X11R6
273156/usr/local
232342/usr/obj/usr/src/sys
230268/usr/obj/usr/src/sys/LAPTOP
204636/usr/src/contrib
170340/usr/obj/usr/src/sys/LAPTOP/modules
170338/usr/obj/usr/src/sys/LAPTOP/modules/usr
170336/usr/obj/usr/src/sys/LAPTOP/modules/usr/src
170334/usr/obj/usr/src/sys/LAPTOP/modules/usr/src/sys
170332/usr/obj/usr/src/sys/LAPTOP/modules/usr/src/sys/modules
148210/usr/X11R6/lib
129236/usr/compat
129234/usr/compat/linux
116012/usr/compat/linux/usr
106724/usr/obj/usr/src/gnu
105986/usr/obj/usr/src/tmp
101880/usr/src/sys
100536/usr/obj/usr/src/tmp/usr
88956/usr/compat/linux/usr/lib
88856/usr/obj/usr/src/gnu/usr.bin
86464/usr/X11R6/share
83186/usr/local/share
79184/usr/local/lib
78854/usr/share
67228/usr/compat/linux/usr/lib/locale
61072/usr/obj/usr/src/lib
59326/usr/local/freebsd-update
59324/usr/local/freebsd-update/work
56616/usr/X11R6/lib/X11
52090/usr/obj/usr/src/tmp/usr/src
49418/usr/obj/usr/src/tmp/usr/src/gnu
49416/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin
47864/usr/src/contrib/gcc
45808/usr/obj/usr/src/gnu/usr.bin/cc
44264/usr/X11R6/lib/X11/fonts
43932/usr/ports/distfiles
40422/usr/X11R6/share/doc
39098/usr/src/sys/dev
38956/usr/obj/usr/src/usr.sbin
37694/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc
33638/usr/share/doc
32104/usr/ports/devel
31654/usr/local/lib/perl5
31646/usr/lib
31414/usr/X11R6/lib/firefox
31082/usr/local/freebsd-update/work/4
30496/usr/compat/linux/usr/lib/locale/locale-archive
30218/usr/share/doc/en_US.ISO8859-1
28974/usr/local/lib/perl5/5.8.8
28080/usr/src/contrib/binutils
26840/usr/ports/www
26692/usr/src/crypto
26288/usr/local/share/doc
26166/usr/local/freebsd-update/work/3
25830/usr/X11R6/bin
24344/usr/bin
24190/usr/compat/linux/usr/share
24124/usr/X11R6/include
23604/usr/X11R6/share/doc/qt
23602/usr/X11R6/share/doc/qt/html
23142/usr/share/doc/en_US.ISO8859-1/books
21592/usr/X11R6/lib/firefox/components
21436/usr/local/bin
21240/usr/ports/games
20528/usr/obj/usr/src/usr.bin
19966/usr/src/lib
19820/usr/obj/usr/src/tmp/usr/lib
19572/usr/obj/usr/src/secure
19552/usr/ports/INDEX-6.db
19072/usr/obj/usr/src/sys/LAPTOP/kernel.debug
18534/usr/src/share
18488/usr/share/man
18464/usr/obj/usr/src/lib/libc
17866/usr/obj/usr/src/gnu/lib
16902/usr/src/contrib/bind9
16500/usr/obj/usr/src/secure/lib
16206/usr/src/sys/contrib
15788/usr/src/contrib/gdb
15758/usr/libexec
15666/usr/X11R6/include/firefox
15590/usr/obj/usr/src/gnu/usr.bin/cc/cc_int
15538/usr/local/freebsd-update/work/4/rollback
15538/usr/local/freebsd-update/work/4/install
15462/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int
15348/usr/obj/usr/src/gnu/usr.bin/gdb
15312/usr/src/usr.sbin
15208/usr/ports/net
14984/usr/X11R6/lib/X11/fonts/100dpi
14934/usr/X11R6/share/locale
14688/usr/ports/graphics
14546

RE: compiling error - /usr : filesystem full

2007-02-08 Thread Michael K. Smith - Adhost
Hell Don:

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:owner-freebsd-
 [EMAIL PROTECTED] On Behalf Of Don Munyak
 Sent: Thursday, February 08, 2007 10:58 AM
 To: FreeBSD Questions
 Subject: Re: compiling error - /usr : filesystem full
 
 Here's some additional Information I have been able to find. The
 narrative is just to further explain what I was doing.
 -
 I was in the process of rebuilding a new kernel for one of my laptops.
 I did the whole cvsup_without-gui. I created a new kernel called
 LAPTOP and commented all unnecessary drivers and options.
 
 When I ran make buildkernel KERNCONF=LAPTOP, the process eventually
 died with an error. I neglected to write down the exact error, but it
 was something like
 
 {objcopy) /usr : filesystem full
 
 As you can see /usr is choking. I have not turned off the laptop.
 Based on the information below, what can I delete to free up some
 space. I use the word delete in broad terms. Much like the windows
 world where you should 'uninstall' as opposed to simply deleting a
 folder...I am not sure what to do...ie how to free up space.
 
 The only thing I can think of is to simply # rm /usr/ports ... for
 lack of a better example.
 
 # du -ak /usr |sort -nr |  /tmp/file2.txt
 This file had 24,000 lines so I deleted much of the file.
 
 Your thoughts/suggestions will be much appreciated.
 
 
 
 ### output from running # df -m  /tmp/file1.txt
 ### where -m is MB
 Filesystem  1M-blocks Used Avail Capacity  Mounted on
 /dev/ad0s1a   495   55   40012%/
 devfs   00 0   100%/dev
 /dev/ad0s1e   495   10   445 2%/tmp
 /dev/ad0s1f  2300 2286  -170   108%/usr
 /dev/ad0s1d  1098   58   952 6%/var
 devfs   00 0   100%/var/named/dev
 
 
 ### output from running # du -ak /usr |sort -nr |  /tmp/file2.txt
 ### where -a is 'display entry for each file in file hierarchy
 ### where -k is 'display block count in kilobyte'
 2341378/usr
 636728/usr/obj
 636726/usr/obj/usr
 636724/usr/obj/usr/src

snip

This is from
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

4.6 Remove /usr/obj
As parts of the system are rebuilt they are placed in directories which
(by default) go under /usr/obj. The directories shadow those under
/usr/src.

You can speed up the make buildworld process, and possibly save yourself
some dependency headaches by removing this directory as well.

Some files below /usr/obj may have the immutable flag set (see
chflags(1) for more information) which must be removed first.

# cd /usr/obj
# chflags -R noschg *
# rm -rf *

---

That might get you enough room.

Regards,

Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: compiling error - /usr : filesystem full

2007-02-08 Thread Robert Huff


  {objcopy) /usr : filesystem full
  
  The only thing I can think of is to simply # rm /usr/ports ... for
  lack of a better example.
  
  # du -ak /usr |sort -nr |  /tmp/file2.txt
  This file had 24,000 lines so I deleted much of the file.
  
  Your thoughts/suggestions will be much appreciated.

1) make the above:

du -k | sort -nr | head -n 30

Whatever's causing your problem is likely to reveal itself in
the list of the 30 largest directories.


  Filesystem  1M-blocks Used Avail Capacity  Mounted on
  /dev/ad0s1a   495   55   40012%/
  devfs   00 0   100%/dev
  /dev/ad0s1e   495   10   445 2%/tmp
  /dev/ad0s1f  2300 2286  -170   108%/usr

2) Depending on your installation, 2gb is _small_ for /usr.  IF
that's what you have, then you need to be ruthlessly pro-active
about purging unneeded files.
Start by running the command above as a cron job once a day;
mail yourself the output.

3) As others mentioned, rm -r /usr/obj/* before make
buildworld.  On my system, it takes up 863 mb.

4)a Install ports-mgt/portupgrade.
  b run /usr/local/sbin/portsclean -CDD



Robert Huff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


compiling error - /usr : filesystem full

2007-02-07 Thread Don Munyak

Hello,

I was recompiling the kernel on my laptop when the process ended with errors.

/usr : filesystem full

I suspect that the HD is has too many files ??

can I simply remove/delete to ports from /usr/ports and try to recompile?

btw...I have used pkg_add in the past. Will deleting the ports files
tantamount to deleteing a folder in windows without uninstalling first
?

Thanks

Don
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: compiling error - /usr : filesystem full

2007-02-07 Thread Garrett Cooper

On Wed, 7 Feb 2007, Don Munyak wrote:

 Hello,

 I was recompiling the kernel on my laptop when the process ended with 
errors.


 /usr : filesystem full

 I suspect that the HD is has too many files ??

 can I simply remove/delete to ports from /usr/ports and try to recompile?

 btw...I have used pkg_add in the past. Will deleting the ports files
 tantamount to deleteing a folder in windows without uninstalling first
 ?

 Thanks

 Don

If you used the default cluster size, it's probably too small of a slice 
to hold all of the file entries resulting in a large amount of internal 
fragmentation.


Delete the files and look up tunefs for how to resize your slice's 
cluster size--make sure to do this in single user mode.


-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: compiling error - /usr : filesystem full

2007-02-07 Thread [EMAIL PROTECTED]

On 07/02/07, Don Munyak [EMAIL PROTECTED] wrote:

Hello,

I was recompiling the kernel on my laptop when the process ended with errors.

 /usr : filesystem full

I suspect that the HD is has too many files ??

can I simply remove/delete to ports from /usr/ports and try to recompile?

btw...I have used pkg_add in the past. Will deleting the ports files
tantamount to deleteing a folder in windows without uninstalling first


By default pkg_add (and installing from ports tree)
records the relevant information in /var/db/pkg/,
deleting /usr/ports will not affect your ability to pkg_add
or pkg_delete (pkg_deinstall?) in the least, though
it will deeply hinder your ability to install from ports.
If you have the option, move /usr/obj to some other
drive, even if not, and assuming you have extra space
on some other partition (if /home is particularly barren),
you can create a directory and symlink it to /usr/obj.

% ls -l /usr
total 44
lrwxr-xr-x   1 root  wheel16 Feb 10  2006 X11R6 - /usr/local/X11R6
drwxr-xr-x   2 root  wheel  7168 Jan 17 09:54 bin
drwxr-xr-x   2 root  wheel   512 Feb 10  2006 compat
drwxr-xr-x   2 root  wheel   512 Jan 17 09:48 games
lrwxr-xr-x   1 root  wheel 5 Feb 10  2006 home - /home
drwxr-xr-x  47 root  wheel  4608 Jan 17 09:46 include
drwxr-xr-x   4 root  wheel  8704 Jan 17 09:54 lib
drwxr-xr-x   5 root  wheel   512 Feb 10  2006 libdata
drwxr-xr-x   5 root  wheel  1536 Jan 17 09:54 libexec
drwxr-xr-x  16 root  wheel   512 Nov 12 17:47 local
lrwxr-xr-x   1 root  wheel 9 Nov  4 11:45 obj - /home/obj
lrwxr-xr-x   1 root  wheel 6 Feb 10  2006 ports - /ports
drwxr-xr-x   2 root  wheel  5120 Jan 17 09:54 sbin
drwxr-xr-x  27 root  wheel   512 Feb 10  2006 share
lrwxr-xr-x   1 root  wheel 9 Nov  2 12:13 src - /home/src
drwxr-xr-x   3 root  wheel   512 Dec 17 16:01 tmp


--
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]