From owner-freebsd-questions Mon Apr 27 20:37:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26766 for freebsd-questions-outgoing; Mon, 27 Apr 1998 20:37:47 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from kamidake.apricot.com (root@kamidake.apricot.com [170.1.160.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26742 for ; Mon, 27 Apr 1998 20:37:41 -0700 (PDT) (envelope-from scanner@apricot.com) Received: from ryoohki.apricot.com (scanner@ryoohki.apricot.com [170.1.160.34]) by kamidake.apricot.com (8.8.8/8.8.8) with ESMTP id UAA01078 for ; Mon, 27 Apr 1998 20:36:47 -0700 (PDT) Received: from ryoohki.apricot.com (scanner@localhost) by ryoohki.apricot.com (8.6.12/8.6.12) with ESMTP id UAA03664 for ; Mon, 27 Apr 1998 20:35:31 -0700 Message-Id: <199804280335.UAA03664@ryoohki.apricot.com> X-Authentication-Warning: ryoohki.apricot.com: scanner owned process doing -bs To: questions@FreeBSD.ORG Subject: lockups on machine with NFS writes to itself.. Reply-To: scanner@apricot.com X-URI: http://www.apricot.com/~scanner/ X-Face: 6K2.ZvQgQ.NDQLIx.1pW(xRu*">:}&PX-Ad_!!?wU7H4L"wF"0xEwYu=8Or0V+=5?-eO1XL 7-0Hom/|]B2C7Uznyol-NVnvEk:+sod^MyB4v4qVpPDemr;b@pZdRSXu.'Gm^t0?2l,j[&t.kbc[UW x6Lz^e$K$W Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Apr 1998 20:35:31 -0700 From: Scanner Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have recently installed a machine FreeBSD 2.2.6. This machine has an 8.4gig IDE drive and a 4gig UW Seagate attached to an Adaptec 2940UW. The machine has 64mb of RAM, with a plain intel P166. When a user is doing some large writes to partitions mounted via NFS on the local machine (using amd.. I am not sure why the linkfs option is not working although the same maps work on other machines) the machine nfs server will hang and eventually the whole machine crashes and reboots. In the logs I only have messages like these: Apr 27 12:19:38 kamidake /kernel: nfs server kamidake.apricot.com:/extra3/home/p omru: not responding Apr 27 12:22:23 kamidake /kernel: nfs server kamidake.apricot.com:/extra3/home/z ed: not responding .... some stat messages from popper edited out ... Apr 27 12:46:36 kamidake /kernel: nfs server kamidake.apricot.com:/extra3/home/e merson: not responding Apr 27 12:49:19 kamidake /kernel: Out of mbuf clusters - increase maxusers! Apr 27 19:58:27 kamidake /kernel: Copyright (c) 1992-1998 FreeBSD Inc. I had already (before this) increased MAXUSERS to be 20. Is this indeed the problem? Should I up MAXUSERS again? If so, how far? Right now I am going to up it to 40 since the machine should have more than enough resources to handle the extra space that entails. Another annoying problem is that when the machine crashes, it does not come up all the way. Yes, the it comes up, fscks the partitions since it did not shut down gracefully, it then says it could not remount / since it was dirty and sits waiting for me to to tell it what shell to use. Did it not used to, if it fsck'd /, reboot then to do the remount? Any help is appreciated. --Scanner (scanner@apricot.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message