*BSD News Article 98793


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!uunet!in1.uu.net!206.252.192.28!news.stealth.net!news.maxwell.syr.edu!news-peer.sprintlink.net!news-west.sprintlink.net!news.sprintlink.net!Sprint!news.primenet.com!bkogawa
From: bkogawa@primenet.com (Bryan Ogawa)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Out of INODES
Date: 27 Jun 1997 13:31:00 -0700
Organization: Primenet Services for the Internet
Lines: 21
Message-ID: <5p17u4$8oq@nntp02.primenet.com>
References: <01bc830e$a0ffc9f0$0f00a8c0@kahuna>
X-Posted-By: bkogawa@206.165.6.206 (bkogawa)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:43773

"Kurt Schafer" <kschafer@cyberbeach.net> writes:

>I received an error that one of the directories I've got set up as a
>repository for USENET articles is out of inodes.

>The drive is a 4gig barracuda of which 1.2gigs are taken up. But god knows
>how many actual files and directories are hogging inodes.

>The machine is an INND server with the /var/news distributed amongst 4 4gig
>drives via symlinks to different tree hierarchies. (alt rec, etc)

You will need to reformat the drive. AFAIK, this is the only way to
increase the number of inodes.  It's a flag to newfs (-i, according to the
man page).  There is a formula somewhere (the INN FAQ, I believe) which
suggests what this number should be, I believe.

>Any pointers would be welcome.

>- Kurt
--
bryan k. ogawa  <bkogawa@primenet.com>  <bkogawa@netvoyage.net>