From owner-freebsd-bugs  Fri Dec 13 04:57:15 1996
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id EAA15008
          for bugs-outgoing; Fri, 13 Dec 1996 04:57:15 -0800 (PST)
Received: from cc.acnit.ac.ru (cc.acnit.ac.ru [147.45.142.18])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA14960;
          Fri, 13 Dec 1996 04:56:34 -0800 (PST)
Received: (from lozenko@localhost) by cc.acnit.ac.ru (8.7.5/8.7.3) id PAA04966; Fri, 13 Dec 1996 15:57:21 +0300 (MSK)
Date: Fri, 13 Dec 96 12:57:20 +0000
From: lozenko@cc.acnit.ac.ru (Evgeny A. Lozenko)
To: freebsd-bugs@freebsd.org
Cc: bugs@freebsd.org
Message-ID: <ABmALioSq4@cc.acnit.ac.ru>
Subject: Re:NFS client can kill FreeBSD 2.1.5
X-Mailer: BML [UNIX Beauty Mail v.1.39]
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>As Evgeny A. Lozenko wrote:

>>  Kernel reports "kernel/ out of swap space", any processes starts
>> after this are killed.

>Well, so you ran out of swap space. :-}
 Yes, we have 8MB RAM and only 16M swap space(average filling up by 10-12 MB)

>>  Whats happened? Why NFS client can kill FreeBSD?This is FreeBSD
>> bug or no?

>It's not a bug... you're overloading the machine.  You need to figure
>out either which processes were the real culprits (run `top' on the

 If it's not a FreeBSD bug , why the same actions from another FreeBSD 2.1.5 in
our LAN ( such as volume mounting and read/write ) don't kill NFS server ,
when we perform these actions one NFS connection gets about of 0K :( .

                                Eugeny , Vasily .