Build world & build kernel question
jerrymc at clunix.cl.msu.edu
Thu Aug 14 07:04:06 PDT 2003
> Hello everybody,
> please advice me if you know.
> I have my /usr partition 1200 MB big. I ran cvsup, then make world.
> Everything was OK, but then I try build kernel and it stoped with
> error - No inodes free. df show I use /usr to 103% :-)))
> So I cd into /usr/src then make clean. df show 80% free...
> Now I run make kernel again but I'm not sure, if it is not wrong way.
> Can I do it such way ? Doesn't make clean "clean" my previously
> installed binaries (during make world) ?????
make clean just does whatever is under the 'clean' label in the Makefile.
It typically includes removing *.o files and other miscellaneous files
used while building something. That can mean removing binaries, but
usually does not include removing installed binaries.
Anyway, you would have to dig down through the Makefile-s to know
for sure. It is unique for each one.
As for your /usr partition, it depends on what you have in it.
Many people put things like /usr/ports and /usr/local and even /usr/src
and maybe /usr/share into another large file system and make symbolic
links to them. If you have it all in /usr, AND try to do a build
it needs to be very big.
You may also have some other stuff in there left over from some
earlier activity. Go in to /usr and use du(1) to see what is eating
up all the space.
du -sk *
Go in to directories that seem unexpectedly large and do it again
until you find things you can nuke.
You may need to move some things to another file system and
make links or create a larger file system.
As for inodes, each file and directory needs an inode. A certain
number area created when the file system is built. If you don't
specify otherwise the system (newfs) tries to guess an appropriate
number for the size of the file system you are creating. Of course
it is a compromise. If you happen to fill up the file system
with a lot of small files you can use up the number of inodes
before you actually fill the space. On the other hand if you
make a lot of very big files, you can have a lot of created inodes
that don't get used even though the space is all used up.
Check out newfs(8), especially the -i and -f parameters.
/stand/sysinstall does the newfs-ing for you when you initially
build the system, but if something like the number of inodes needs
adjusting, you may need to do this by hand later. Note, that you
can't just rerun newfs. That will wipe out the old file system
and overwrite it with the new one (thus destroying all your existing
> Any advice is very welcome.
> Peter Rosa
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions