Re: UP2000 running out of files _very_ fast!

["Konrad Podloucky" <konrad pelimbert tssc univie ac at>]

On 14-Dec-99 Todd Henderson enlightened me with:
> I just found that a program like this is creating my problem,
> at least
> part of the time.
> 
> If you run this program when the file STOP, or whatever you
> want to put
> in there doesn't exist, it seems to lock out users, rsh
> commands, etc.
> 
Something similar happens here, but not on the UP2000. Sometimes
a job aborts, with the error "File not found" although the file
exists.

The UP which ran out of files yesterday evening was doing fine
this morning. However I've discovered the following messages in
the syslog:
Dec 13 20:53:43 schosulan kernel: VFS: file-max limit 4096
reached

And shortly after that:
Dec 13 20:59:57 schosulan kernel: fault.c:43 spinlock stuck in
klogd at fffffc000032843c(0) owner oc.x at fffffc000032843c(1)
fault.c:43
Dec 13 20:59:57 schosulan kernel: fault.c:43 spinlock grabbed in
klogd at fffffc000032843c(0) 1213 ticks

(oc.x is the "bad" program, but I've also got spinlock messages
from bash, klogd, in.telnetd, sendmail, syslogd in vmscan.c,
sched.c and fault.c) There were 48 of these messages and all at
the same time.
When that happened the system was in "Too many files open"-mode.

Currently I've got cron writing the contents of
/proc/sys/fs/file-nr to a log every 2 minutes and nothing has
happened so far, although the system is under heavy load.

Konrad


________________________________________________________________
  .~.   Konrad Podloucky    <konrad@pelimbert.tssc.univie.ac.at> 
  /V\                       Running GNU/Linux 2.2.13 on an Alpha
 // \\  GnuPG/PGP-key available by request  
/(   )\   
 ^^-^^    "Smile -- It irritates people."