From owner-freebsd-current@FreeBSD.ORG Mon Jan 12 14:58:45 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 8304116A4D0 for ; Mon, 12 Jan 2004 14:58:45 -0800 (PST) Received: from web14101.mail.yahoo.com (web14101.mail.yahoo.com [216.136.172.131]) by mx1.FreeBSD.org (Postfix) with SMTP id 11D4643D58 for ; Mon, 12 Jan 2004 14:58:43 -0800 (PST) (envelope-from cguttesen@yahoo.dk) Message-ID: <20040112225842.60618.qmail@web14101.mail.yahoo.com> Received: from [194.248.174.33] by web14101.mail.yahoo.com via HTTP; Mon, 12 Jan 2004 23:58:42 CET Date: Mon, 12 Jan 2004 23:58:42 +0100 (CET) From: =?iso-8859-1?q?Claus=20Guttesen?= To: Mikhail Teterin , current@FreeBSD.org In-Reply-To: <200401121501.i0CF1eMC047055@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: core-dumping over NFS 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: Mon, 12 Jan 2004 22:58:45 -0000 > I've observed the following bad behaviour of > -current mostly related > to dumping core of a buggy program over the NFS. > > The mounts are regular and default (v3?), except for > the ``intr'' flag. > No rpc.lock or anything... > > Any comments? Setting up an 5.2 (yehaa) nfs-server. Did some network-testing witohout doing any changes to nfs on client and server, just a plain mount. Throughput was mere 16 Mbit pr. sec. on a 100 Mbit network. One thread suggested the usage of TCP and some changes to the rd-rw-size on the client. So I did the changes. My fstab look like this: jasmin:/home/claus /home/claus/jasmin nfs rw,tcp,intr,nfsv3,-w=32768,-r=32768 0 0 The throughput rose to 77 Mbit per. sec. /etc/rc.conf's nfs_server_flags changed to: nfs_server_flags="-t -u -n 8" Eventhough this may not be directly related to your problem, you could try to switch to TCP and change the client-fstab as mentioned above. The server is a dual pentium III at 1 Ghz, 1.5 GB RAM, client likewise. Running RC2 for a week now on both client and server without any hickups. Server is running two instances of seti@home to keep it at 100 % CPU-util. Copied a 647 MB large file back and forth while testing nfs-settings, diff'ed the file. No problem what so ever. regards Claus Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan