Subject: Re: stuck with filled vnode table
To: Todd Vierling , Christos Zoulas <christos@zoulas.com>
From: Objects In Mirror Are Closer Than They Appear <greywolf@starwolf.com>
List: current-users
Date: 02/02/1999 09:00:09
% limit
cputime         unlimited
filesize        unlimited
datasize        65536 kbytes
stacksize       512 kbytes
coredumpsize    unlimited
memoryuse       61832 kbytes
descriptors     64
memorylocked    20610 kbytes
maxproc         80
% pstat -T
117/1772 files
    774 vnodes
0M/129M swap space
% unlimit descriptors (or ofiles, depending on tcsh/csh)
cputime         unlimited
filesize        unlimited
datasize        65536 kbytes
stacksize       512 kbytes
coredumpsize    unlimited
memoryuse       61832 kbytes
descriptors     1772
memorylocked    20610 kbytes
maxproc         80
%

If root has unlimited his access, I could see where the _file_ table
would be reported as full; I was under the impression that the vnodes
listed by pstat was the size of the _cache_, and not the size of the
internal table, and that filling the cache was not fatal.

Shows what happens when you assume...


				--*greywolf;
--
Microsoft Windows NT -- "What a totally excellent discovery...NOT!"