Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!news.kei.com!news.mathworks.com!fu-berlin.de!news.gtn.com!klemm.gtn.com!usenet From: andreas@klemm.gtn.com (Andreas Klemm) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: kernel recompile weirdness Date: 9 Feb 1997 13:36:39 GMT Organization: FreeBSD makes fun Lines: 44 Message-ID: <5dkjt7$1kv@klemm.gtn.com> References: <Pine.BSF.3.91.970209035913.9709A-100000@hack.txonline.net> NNTP-Posting-Host: klemm.gtn.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Newsreader: knews 0.9.8 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:35228 In article <Pine.BSF.3.91.970209035913.9709A-100000@hack.txonline.net>, Spam This! <abuser@txonline.net> writes: > i've recompiled the kernel several times on a wide variety of machines > ranging from 486s with 8mb to pentiums with 40mb of ram with bsd 2.1.5 > and always get 'out of inodes' upon installing the new kernel and > rebooting. what causes this? What does the following command produce ?! $ df -i Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted /dev/sd0a 31775 15688 13545 54% 1049 6629 14% / /dev/sd0s3e 63567 17841 40641 31% 1857 13501 12% /www /dev/sd0s3f 127151 74557 42422 64% 1192 29526 4% /var /dev/sd0s3g 765058 627134 76720 89% 33145 158853 17% /usr /dev/sd1s1e 193423 129599 48350 73% 57332 31626 64% /news /dev/sd1s1f 1786531 1377191 266418 84% 104013 333745 24% /local Every filesystem has a certain amount of inodes. Every file and directory is stored in the inode list. So couls it be the case, that you have created too few filesystems, so that your root or /usr filesystems runs out of inodes, because you have many files on it ?! Normally this is only the case when having News filesystems not in /usr/src ... Check it out. The best way to get rid of this is a complete dump of all filesystems and to use the fixit floppy to newfs every filesystems, that needs more inodes and restore your backup. Be careful when using dump, don't use a blocksize > 32K, since restore wouldn't be able to read a dump afterwards ... In FreeBSD 2.2 and -current I'm sure, that it's documented in the manpage and that dump doesn't accept values over 32K. See newfs, how to create more inodes ... Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<<