Date: Tue, 28 Mar 2006 20:34:18 +0100 From: Chris <chrcoluk@gmail.com> To: freebsd-stable@freebsd.org Subject: nmbclusters Message-ID: <3aaaa3a0603281134sd0d4e16x@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Using 6.0 release latest security branch. netstat -m 69/576/645 mbufs in use (current/cache/total) 65/261/326/33792 mbuf clusters in use (current/cache/total/max) 0/38/8704 sfbufs in use (current/peak/max) 147K/666K/813K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 29780 requests for I/O initiated by sendfile 633 calls to protocol drain routines sysctl kern.ipc.nmbclusters kern.ipc.nmbclusters: 65536 sysctl kern.ipc.nmbclusters=3D25000 kern.ipc.nmbclusters: 65536 -> 25000 70/575/645 mbufs in use (current/cache/total) 64/262/326/33792 mbuf clusters in use (current/cache/total/max) 0/38/8704 sfbufs in use (current/peak/max) 145K/667K/813K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 29780 requests for I/O initiated by sendfile 633 calls to protocol drain routines so the sysctl variable has no affect, has this become a read only tunable again only settable in loader.conf? if yes then their is a bug where it shows no error on sysctl command, or is it suppoedbly settable then their is a bug where it doesnt work or netstat -m shows inccorect info. Or is this setting been depreciated? Also if the machine stops responding, and no kernel panic logged does it mean a livelock/deadlock? Have been seeing issues on 3 diff 6.0 release servers which simply go dead. 2 were rolled back to 5.4 and immediatly became stable and I left this one on 6.0 to try and resolve problems but diffilcult with no log entries. Thanks Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3aaaa3a0603281134sd0d4e16x>