Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Apr 2003 08:55:46 -0400
From:      Bill Moran <wmoran@potentialtech.com>
To:        freebsdQ0@richardshea.fastmail.fm
Cc:        freebsd-questions@freebsd.org
Subject:   Re: upping MBUFS even though netstat -m says PEAK is low ?
Message-ID:  <3EA93052.2010409@potentialtech.com>
In-Reply-To: <3EA9A69B.16198.16C5739@localhost>
References:  <3EA9A69B.16198.16C5739@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
Richard Shea wrote:
> 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 ...

Doesn't look like mbufs are the limiting factor.

Perhaps try increasing net.inet.tcp.recvspace

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EA93052.2010409>