Xref: utzoo news.sysadmin:3722 news.software.b:7702 comp.unix.aix:5003
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!ukc!warwick!cudep
From: cudep@warwick.ac.uk (Ian Dickinson)
Newsgroups: news.sysadmin,news.software.b,comp.unix.aix
Subject: Re: IBM RS/6000 unsuitable for news
Message-ID: <=$L_1=-@warwick.ac.uk>
Date: 9 May 91 08:41:45 GMT
References: <BGLENDEN.91May6130729@colobus.cv.nrao.edu> <1991May07.160042.28634@turnkey.tcc.com> <731@rufus.UUCP>
Sender: news@warwick.ac.uk (Network news)
Organization: Team Limpid's Pink Boy For Bob
Lines: 23
Nntp-Posting-Host: thistle

In article <731@rufus.UUCP> drake@drake.almaden.ibm.com writes:
>This isn't an issue.  When a filesystem is created (or later expanded),
>the number of inodes is set to the number of 4K blocks in the filesystem.
>In other words, except in cases where there are zero length files in the
>filesystem, it's impossible to run out of inodes.
>It's true that the number is "fixed", but only in that you can't change it.
>But the default is always "big enough".

Saying something "simply isn't the case" doesn't change the world around you.

/usr/spool/news (or wherever) is the classic case of not having enough
inodes and the system often refusing to allow you to tune it.

Certainly, on every system I've come across, the default is *NOT*
"big enough" for news.  And it's only recently that more manufacturers
have allowed you to muck around with the number of inodes per partition.

( 4k block sizes for news? *UGH*! )
-- 
\/ato                                                               /'\  /`\
Ian Dickinson                  TED KALDIS FOR PRESIDENT!           /^^^\/^^^\
vato@warwick.ac.uk                                                /TWIN/TEATS\
@c=GB@o=University of Warwick@ou=Computing Services@cn=Ian Dickinson  /       \