From owner-freebsd-stable Wed May 5 11:34:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 0105614EB8 for ; Wed, 5 May 1999 11:34:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA01140; Wed, 5 May 1999 11:33:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905051833.LAA01140@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lambert@warped.cswnet.com Cc: freebsd-stable@freebsd.org Subject: Re: 256MB mail server with 190+MB inactive? In-reply-to: Your message of "Tue, 04 May 1999 15:31:40 CDT." <199905041449.5717287.6@warped.cswnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 May 1999 11:33:16 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The 64MB system was running about 9MB into swap at all times and used 20 - > 25MB for cache, ~23MB active, 10-15MB wired, and between 490K and 3MB > free. The rest was inact or buf. We had a few problems with users timing > out while checking their mail. > > The 256MB server went up this morning and is seeing real load for the > first time. It hung after 5 hours of uptime. We had to push the reset > button to recover. It was still responding to pings and would switch > between virtual consoles. You could enter a username at the login prompt > but would not get a password prompt. Ctrl-Alt-Del did not work to reload > the box. > > Now it's back up and has been up for 3:30. Current memory stats from top > are: > > Mem: 23M Active, 189M Inact, 19M Wired, 12M Cache, 8330K Buf, 6512K Free > 120 processes, 118 sleeping. > > The rpc.statd process shows to be using 257M with 468K resident. Er, why are you running statd at all? Are you using NFS to access user mailboxes? You should know better than that. If you are, you are probably running into NFS issues. It does sound like you had the entire filesystem locked, which would suggest NFS or some similar culprit. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message