Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!paladin.american.edu!europa.eng.gtefsd.com!uunet!newsflash.concordia.ca!sifon!homer.cs.mcgill.ca!storm
From: storm@cs.mcgill.ca (Marc WANDSCHNEIDER)
Newsgroups: comp.os.386bsd.questions
Subject: Re: out of inodes! - HELP!
Date: 7 Jan 1994 15:29:38 GMT
Organization: SOCS, McGill University, Montreal, Canada
Lines: 36
Message-ID: <2gjv52$gol@homer.cs.mcgill.ca>
References: <2gk70i$8t@twitch.ns.doe.gov>
NNTP-Posting-Host: mnementh.cs.mcgill.ca
In article <2gk70i$8t@twitch.ns.doe.gov>,
James Martin <martinj@havoc.ns.doe.gov> wrote:
>
>twitch /netbsd: uid101 on /var/spool/news: out of inodes
>
>I assume inodes are the things that keep info about a
>file or someting equally unplesant, and I've run out of
>the miserable things... Can this be solved by a simply
>kernel rebuild, or am I looking at reformating the
>disk, or something even worse?
unfortunately, the number of allowed inodes is part of the
fiesystem construction when you run newfs.
what you want to do is recreate the file system with the
-i 1024, which creates an inode for every 1024 bytes instead
of every 2048 bytes of disk space.
you might also be able to use 512, if your fragment size for the
filesystem is also 512. i'd recommend trying
newfs part name -b 4096 -f 512 -i 1024
[or change the last one to 512].
the problem is that most inn articles aren't all that large, and
thus, not enough inodes are allocated always.
marc'em.
--
-----------------------------------------------------------------------------
Marc Wandschneider Seattle, WA
"well, do you, like, know where west virginia is?" - a [very] american
tourist to a texan atop the eiffel tour.