From owner-freebsd-questions@FreeBSD.ORG Fri Apr 25 02:21:18 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4348237B401 for ; Fri, 25 Apr 2003 02:21:18 -0700 (PDT) Received: from smtp-1.paradise.net.nz (smtp-1a.paradise.net.nz [202.0.32.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A6B643F75 for ; Fri, 25 Apr 2003 02:21:16 -0700 (PDT) (envelope-from rshea@thecubagroup.com) Received: from ss11232 (203-79-125-175.adsl.paradise.net.nz [203.79.125.175]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id DF90884E87 for ; Fri, 25 Apr 2003 21:21:13 +1200 (NZST) From: "Richard Shea" To: freebsd-questions@freebsd.org Date: Fri, 25 Apr 2003 21:20:27 +1200 MIME-Version: 1.0 Message-ID: <3EA9A69B.16198.16C5739@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: upping MBUFS even though netstat -m says PEAK is low ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsdQ0@richardshea.fastmail.fm List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2003 09:21:18 -0000 Hi - I often get the message "Missed packet -- no receive buffer" appearing on the console. I have read around and some people advise fixing this by changing the value of MBUFS. Before I do that I wanted to check something out. When I do netstat - m at the time I'm getting these messages on the screen I see ... 10/48/4096 mbufs in use (current/peak/max): 8 mbufs allocated to data 2 mbufs allocated to packet headers 2/28/1024 mbuf clusters in use (current/peak/max) 68 Kbytes allocated to network (2% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines ... now does the fact that the peak value of mbufs is only 48 means that changing MBUFS max is hardly likely to do away with this problem ? BTW strange aspect of this - I'm pretty sure the only time this error occurs is when a W2000 box is running backup and writing the backup file to a Samba share on the FBSD box. In truth the FBSD box does not normally get intensively used across the network for any other reason and so this may not be significant but I thought I would mention it ... Regards richard.