Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!tut.cis.ohio-state.edu!husc6!ogccse!cvedc!nosun!illian!sopwith!snoopy
From: snoopy@sopwith.UUCP (Snoopy)
Newsgroups: comp.sys.sequent
Subject: Re: Running out of inodes
Summary: Try running mkfs directly?
Message-ID: <193@sopwith.UUCP>
Date: 1 Jun 89 16:02:21 GMT
References: <1033@syma.sussex.ac.uk>
Reply-To: snoopy@sopwith.UUCP (Snoopy)
Organization: The Daisy Hill Puppy Farm
Lines: 22

In article <1033@syma.sussex.ac.uk> andy@syma.sussex.ac.uk (Andy Clews) writes:

|Trouble is, we find that no matter what number is supplied with the -i
|option to newsfs, the file system is rebuilt with exactly the same
|number as before (i.e. 36864 inodes on a 254Mb partition)! We asked for
|twice the current number of inodes.
|
|Anyone know what might be happening here? Is newfs simply ignoring the
|option or is something else overriding it? We ran newfs(8) also with the
|-v (verbose) option, and it appeared from the diagnostics that our
|requested number of inodes was not being passed on to mkfs. 

Sounds odd.  As a workaround, you could try running newfs -v to get
all the magic numbers, and then running mkfs directly, tweaking the
'nbpi' argument as desired.  Unless Sequent has done something unusual,
newfs is merely a friendly front-end to mkfs.

    _____     						  .-----.
   /_____\    Snoopy					./  RIP	 \.
  /_______\   qiclab!sopwith!snoopy			|  	  |
    |___|     parsely!sopwith!snoopy			| tekecs  |
    |___|     sun!nosun!illian!sopwith!snoopy		|_________|