Date: Sat, 8 May 1999 13:48:08 -0500 (CDT) From: Kevin Day <toasty@nfs.dragondata.com> To: toasty@nfs.dragondata.com (Kevin Day) Cc: dillon@apollo.backplane.com (Matthew Dillon), toasty@home.dragondata.com (Kevin Day), current@FreeBSD.ORG Subject: Re: -current NFS crash (out of mbuf clusters) Message-ID: <199905081848.NAA14356@nfs.dragondata.com> In-Reply-To: <199905081842.NAA14324@nfs.dragondata.com> from Kevin Day at "May 8, 1999 01:42:27 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Erm, sorry guys, that huge message wasn't intended to go back to -current, just Matt. My apologies. :) Kevin > > :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 > > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) > 0 1 0 0 10 0 500 0 wait Is ?? 0:00.00 (init) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905081848.NAA14356>