Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!amdcad!lll-crg!gymble!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: "inode: table is full" - a question
Message-ID: <354@umcp-cs.UUCP>
Date: Mon, 17-Mar-86 08:53:44 EST
Article-I.D.: umcp-cs.354
Posted: Mon Mar 17 08:53:44 1986
Date-Received: Tue, 18-Mar-86 08:37:54 EST
References: <154@Shasta.ARPA>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 26

[It is clear from your message that this is a 4.2BSD system.]

Reconfigure and recompile the kernel with a bigger MAXUSERS, or
change the value of `ninode' in the existing kernel and/or the
definition of NINODE in conf/param.c.  If you just need more inode
table space and are happy with your current MAXUSERS, the following
will fix things up:

	% su
	<password>
	# adb -w /vmunix
	ninode?D
	<will print something like `_ninode: 356'>
	ninode?W 0t<new, larger number, eg 512>
	<will print something like `_ninode: 164 = 200'>
	<type control-D here>
	# shutdown <parameters>
	<eventually, it shuts down>
	# fastboot

Read the documentation on `configuring a 4.2BSD system'; it explains
all this stuff somewhere (I think).
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu