From owner-freebsd-current Sat May 8 11:26:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A60714F6A for ; Sat, 8 May 1999 11:26:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA55323; Sat, 8 May 1999 11:26:45 -0700 (PDT) (envelope-from dillon) Date: Sat, 8 May 1999 11:26:45 -0700 (PDT) From: Matthew Dillon Message-Id: <199905081826.LAA55323@apollo.backplane.com> To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -current NFS crash (out of mbuf clusters) References: <199905080833.DAA19171@home.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm sure by now Matt is gonna kill me. :) : :-current from 2 days ago. : :IdlePTD 3096576 :initial pcb at 27ea40 :panicstr: Out of mbuf clusters :panic messages: :--- :panic: Out of mbuf clusters This is probably not NFS related unless there is a leak somewhere. You may have to mess with the NMBCLUSTERS kernel config to increase the number of mbuf clusters. FreeBSD tends to not allocate enough by default in more heavily loaded larger-memory configurations. It should be possible to confirm that the problem is not NFS by taking a general look at the state of the system at the time of the crash. You can run 'ps' and 'netstat' on the core dump: cd /var/crash ps -axl -M vmcore.XX -N kernel.XX netstat -tna -M vmcore.XX -N kernel.XX netstat -m -M vmcore.XX -N kernel.XX -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message