Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!rutgers!att!cbnews!mjs
From: mjs@cbnews.ATT.COM (martin.j.shannon)
Newsgroups: comp.unix.i386
Subject: Re: Still Waiting for Inode fixes, ZZZZZZZZ
Summary: S5 filesystems can only have <65536 inodes!
Keywords: inode, UNIX, news
Message-ID: <12043@cbnews.ATT.COM>
Date: 6 Dec 89 18:19:58 GMT
References: <1989Dec6.023924.1293@virtech.uucp>
Reply-To: mjs@cbnews.ATT.COM (martin.j.shannon,59112,lc,4nr10,201 580 5757)
Organization: AT&T Bell Laboratories
Lines: 21

In article <1989Dec6.023924.1293@virtech.uucp> cpcahil@virtech.uucp (Conor P. Cahill) writes:
>All you have to do is specify the number of inodes that you require
>on the mkfs command line.

Yes, this is true.

>	mkfs /dev/rdsk/0s4 90000:90000

And that's the right syntax, but....

>Creates a 90,000 block file system with 90,000 inodes.

Except that inode numbers are stored in unsigned shorts, so you can't
ever have more than 65535 of them.  The real limit is probably a few
less than 65535, but I don't have access to any current source to
verify what it *really* is.  A *safe* number would be 65500, I'm quite
sure.
-- 
Marty Shannon; AT&T Bell Labs; Liberty Corner, NJ, USA
(Affiliation is given for identification only:
I don't speak for them; they don't speak for me.)