Date: Thu, 27 Jul 2000 00:48:30 +0200 From: Andre Oppermann <oppermann@telehouse.ch> To: hackers@freebsd.org Subject: [Fwd: freeBSD4.0/NFS/EMC] Message-ID: <397F6ABE.6603D6EA@telehouse.ch>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------21DDBE157D2EDE795557DD95
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I'm forwarding this from the qmail mailing list.
Anybody has an idea what might be the problem? Matt?
--
Andre
--------------21DDBE157D2EDE795557DD95
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Return-Path: <qmail-return-51154-andre=pipeline.ch@list.cr.yp.to>
Received: from muncher.math.uic.edu ([131.193.178.181])
by ntmail.pipeline.ch (Netscape Messaging Server 3.62) with SMTP
id 240 for <andre@pipeline.ch>; Wed, 26 Jul 2000 21:39:33 +0200
Received: (qmail 26424 invoked by uid 1002); 26 Jul 2000 19:34:53 -0000
Mailing-List: contact qmail-help@list.cr.yp.to; run by ezmlm
Precedence: bulk
Delivered-To: mailing list qmail@list.cr.yp.to
Received: (qmail 16736 invoked from network); 26 Jul 2000 19:34:53 -0000
Received: from mail9.wlv.netzero.net (209.247.163.66)
by muncher.math.uic.edu with SMTP; 26 Jul 2000 19:34:53 -0000
Received: (qmail 28965 invoked from network); 26 Jul 2000 19:34:30 -0000
Received: from fw2.wlv.netzero.net (HELO michaelb) (209.247.163.243)
by mail9.wlv.netzero.net with SMTP; 26 Jul 2000 19:34:30 -0000
Message-ID: <000101bff738$87f25c60$c1a2640a@michaelb>
From: "M.B." <michaelb@noc.netzero.net>
To: <qmail@list.cr.yp.to>
Subject: freeBSD4.0/NFS/EMC
Date: Wed, 26 Jul 2000 12:34:35 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Mozilla-Status2: 00000000
This was so well written by one of our network engineers and covers
all the questions I need answers for that I just lifted it and am forwarding
to the list for comment/help. I'll just add one additonal error that we
see.
These pop in and out when lots of mail is coming in (usually in alphabetical
order, so in this case, the "b" partition is getting lots of hits on it in a
short
amount of time)
Jul 26 12:23:31 nc4 /kernel: nfs server dm7_1.wlv:/b: is alive again
Jul 26 12:23:54 nc4 /kernel: nfs server dm7_1.wlv:/b: not responding
Jul 26 12:23:54 nc4 /kernel: nfs server dm7_1.wlv:/b: is alive again
Jul 26 12:24:07 nc4 /kernel: nfs server dm7_1.wlv:/b: not responding
Jul 26 12:24:08 nc4 /kernel: nfs server dm7_1.wlv:/b: not responding
Jul 26 12:24:08 nc4 /kernel: nfs server dm7_1.wlv:/b: is alive again
Jul 26 12:24:08 nc4 /kernel: nfs server dm7_1.wlv:/b: is alive again
****following is the text of Keith's questions...
I am wondering if anyone is running FreeBSD 4.0-RELEASE in an NFS-heavy
environment and is noticing performance issues with NFS, or has any tips
on how to tune NFS in the kernel. There are currently 6 identical servers
that we are running FreeBSD on, though they were installed at different
times so some servers are running FreeBSD 3.2-RELEASE, one FreeBSD
3.3-RELEASE, and one FreeBSD 4.0-RELEASE. The machine that is running
FreeBSD 4.0-RELEASE is noticably slower then the other boxes, and thus
handles a lesser amount of email, even though they all have the same
hardware configuration: Dual PIII 600Mhz, 512mb ram, 9.1gb IBM LVD SCSI
system disk, two Intel 100BaseT NICs (it's a server motherboard, so one of
them is integrated). I have 5 more servers that are setup with FreeBSD
4.0 that I want to put into place, but need to figure out what could be
going on to cause this decrease in performance. These boxes are all
running qmail.
The machines are NFS mounting the mail spool directories off of an EMC
Celerra on a dedicated NIC. The other interface is connected to the
outside world where the servers are load balanced behind an Alteon Ace.
Sometimes just a 'df' will take 10-15 seconds to run unless given the -n
switch so it does not try to get new state information.
It's not the backend Celerra since the FreeBSD 3.2 and 3.3 boxes are
running fine, and we have a number of Sun servers attached to the Celerra
as well, with no problems to report. A message that pops up in the
messages file every once and awhile is:
Jul 21 14:17:03 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd03f6a0
Jul 21 14:17:03 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd03f6a0
Jul 21 14:17:05 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd040600
Jul 21 14:17:05 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd040600
Jul 21 14:17:07 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd040890
But, I am not sure what this error message means. I included it because it
*might* have something to do with the problem, and wanted to include
everything I had hoping that someone might have seen this problem before.
My kernel configuration is pretty basic. I enable SMP, disable
I386,486,586 support in the kernel, turn maxusers up to 256, disable USB
support, and recompile the kernel. Nothing fancy on any of the boxes. It
is what someone had configured one of ther boxes, and I just kept it the
same across the board.
qmail is accepting the mail and writing it to the queue, but it never gets
a chance to delivery the email to the NFS-mounted mail spool directories.
For instance, we received couple thousand email messages for usernames
that started with 'b', and these messages piled up on the FreeBSD 4.0
servers, but were delivered immediatly on all of the other machines.
Access to the other partitions mounted off of the same datamover (part of
the Celerra, basically an NFS server) was fine.
Does anyone have any tips or ideas they can pass on to me? I am lost on
what it could be.
Thanks,
--
Keith McCallion
keith@mccallion.com
_____NetZero Free Internet Access and Email______
http://www.netzero.net/download/index.html
--------------21DDBE157D2EDE795557DD95--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?397F6ABE.6603D6EA>