Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!claris!sts!roy
From: roy@sts.sts.UUCP
Newsgroups: comp.unix.wizards
Subject: running out of inodes?
Message-ID: <68000001@sts>
Date: 20 May 89 00:53:00 GMT
Lines: 30
Nf-ID: #N:sts:68000001:000:1700
Nf-From: sts.sts.UUCP!roy    May 19 17:53:00 1989


How does one go about figuring how many inodes a filesystem has?  I've
looked around the man pages quite a bit and the only place I find any
reference to the number of inodes is in mkfs(8).  Our system is a
Sun3/280 running SunOS 4.0.x (where x > 1)

The reason I want to know is, every time I do a man command on a
command with a fair amount of documentation, I get "Word overflow." a
bunch of times and finally "Out of temp file space."  I managed,
through the quota system, to find out how many inodes are actually
being used.  It doesn't look like very much, but I don't know how many
inodes are available, so I can't assume.  I do know that there is
plenty of space available on the filesystem (4M free out of 7M total
on / and 20M free out of 143M total on /var, where /usr/tmp actually
resides), so I figure it must be a problem of running out of inodes.

Anyone have any idea what's going on?  By the way, just to convince
myself there really is enough space in /tmp, I re-directed the output
of an offending man command to a file on my workstation (where
everything is working OK) and transferred that output to /tmp and to
/var/tmp.  No problem, but ... of course we all know there is a
problem.  Thanks for reading my rambling and thanks even more if you
actually consider this problem!

==================================================================
Roy Bixler                   | UUCP: ...!{claris,sun}!sts!roy    |
Semiconductor Test Solutions | Internet: sts!roy@Claris.COM      |
4101 Burton Dr.              | phones: (408) 727-2885 x132 (work)|
Santa Clara, CA  95054	     |         (408) 289-1035      (home)|
==================================================================