From owner-freebsd-hackers Mon Jun 21 7:50:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 7FCA814F37 for ; Mon, 21 Jun 1999 07:50:19 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id HAA12926; Mon, 21 Jun 1999 07:50:17 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <376E5126.43CD80A3@gorean.org> Date: Mon, 21 Jun 1999 07:50:14 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Shaun Jurrens Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Heavily loaded nfs/amd gets stuck References: <19990620032500.B6661@dakota.online.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shaun Jurrens wrote: > Studded, you might try to look at /usr/share/doc/handbook/nfs.html. It might help to use a high quality network card and maybe track the traffic between the boxes to see if the mentioned packet problems show up. It's an Intel motherboard with an Intel Pro 100 built on, plugged into one of two high quality switches running at 100 and full duplex, so I doubt that is the problem. :) I could sniff the traffic, but what would I be looking for? Every DDB backtrace dies in mount() so I am inclined to think it's not a packet problem, but I would be willing to look at just about anything at this point. > Just thought you might have missed the obvious. *Nod* That's always a possibility, NFS is definitely not my thing, although I'm learning more and more about it as I go along. :-/ Thanks, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message