From owner-freebsd-current@FreeBSD.ORG Fri Jul 16 19:15:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D639C16A4CF for ; Fri, 16 Jul 2004 19:15:20 +0000 (GMT) Received: from mail.cems.umn.edu (tyr.cems.umn.edu [134.84.164.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3C4F43D46 for ; Fri, 16 Jul 2004 19:15:20 +0000 (GMT) (envelope-from mwt@cems.umn.edu) Received: from localhost (localhost.cems.umn.edu [127.0.0.1]) by mail.cems.umn.edu (Postfix) with ESMTP id A2A6E14D8E0; Fri, 16 Jul 2004 14:15:45 -0500 (CDT) Received: from mail.cems.umn.edu ([127.0.0.1]) by localhost (tyr.cems.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00697-08; Fri, 16 Jul 2004 14:15:45 -0500 (CDT) Received: from [134.84.164.244] (calamity.cems.umn.edu [134.84.164.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cems.umn.edu (Postfix) with ESMTP id D004714D8CC; Fri, 16 Jul 2004 14:15:38 -0500 (CDT) Message-ID: <40F82941.8010208@cems.umn.edu> Date: Fri, 16 Jul 2004 14:15:13 -0500 From: Mike Thomas User-Agent: Mozilla Thunderbird 0.7 (Macintosh/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson , current@freebsd.org References: <40F8157D.5040104@cems.umn.edu> <40F823CF.40304@centtech.com> In-Reply-To: <40F823CF.40304@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cems.umn.edu Subject: Re: nfsd problems with FreeBSD 5.2.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jul 2004 19:15:21 -0000 Eric Anderson wrote: I'll go through one by one on this. > Hi Mike! I've had some experience with FreeBSD/NFS/NIS and might be > able to help.. (maybe!) > > Have you done a tcpdump to see what traffic is like during that time? Yeah, the packets come in very quickly from several hosts, all via tcp. > > Also - is your NIS server that this mail server is connected to being > used by a lot of clients? I've seen very strange hangs, delays, and > loads when the NIS server doesn't respond quickly enough.. > The NIS server doesn't have a lot of clients, less than 10 off the top of my head, nothing that would cause it to be very slow with responses. > Just for your info, what I use on my clients (I have about 800 NFS > clients), is UDP, NFSv3, 4196 rd/wr size, hard mount, interruptible.. > > Does mountd have a high run time? Maybe it's a mount storm (if you use > automounter on your clients) > Mountd has consumed 0:01 minutes of cpu time with the machine being up two days, since I know of every machine thats mounting the nfs share, I have visited each one individually to make sure the mount was correctly accessable and such (since I was playing with mount options) > What about network interface errors? To be honest, i'm not sure how to check for these, in linux/solaris, ifconfig itself prints out the errors, this isn't the case (at least with ifconfig -a) on FreeBSD, as far as I can tell. > > If you watch an iostat during the busy time, is your disk being slammed? iostat seems to never go over 30k/sec average, > > If you are using uw-imap, how big are the mailboxes? > See, this is the thing that I think may be causing the problems. We are using uw-imap, and the mailboxes vary anywhere from 100k to 600mb (some people are irresponsible mail users!) The thing is though, even in times of high load like someone opening or accessing a mailbox of this size, it shouldn't be causing the box to go down to its knees, should it? I've recompiled the machine with 5.2.1-release-p9 and disabled hyperthreading, we'll see how that goes. --Mike