From owner-freebsd-current@FreeBSD.ORG Mon Jan 12 07:01:49 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 9BABD16A4CE for ; Mon, 12 Jan 2004 07:01:49 -0800 (PST) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DE8243D45 for ; Mon, 12 Jan 2004 07:01:46 -0800 (PST) (envelope-from mi@aldan.algebra.com) Received: from aldan.algebra.com (mi@localhost [127.0.0.1]) by aldan.algebra.com (8.12.10/8.12.10) with ESMTP id i0CF1ftu047056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Jan 2004 10:01:43 -0500 (EST) (envelope-from mi@aldan.algebra.com) Received: (from mi@localhost) by aldan.algebra.com (8.12.10/8.12.10/Submit) id i0CF1eMC047055 for current@FreeBSD.org; Mon, 12 Jan 2004 10:01:40 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <200401121501.i0CF1eMC047055@aldan.algebra.com> To: current@FreeBSD.org Date: Mon, 12 Jan 2004 10:01:39 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w y+z3/UR{6SCQ X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Mon, 12 Jan 2004 10:53:04 -0800 Subject: 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 15:01:49 -0000 Hello! I've observed the following bad behaviour of -current mostly related to dumping core of a buggy program over the NFS. . 5.2-CURRENT (Dec 14) client, Solaris-8 server: created core file is empty (zero sized). . 5.2-CURRENT (Dec 14) server, RedHat-9 client: core is created properly, but sometimes the server goes into a frenzy with the sys-component (bufdaemon) taking up the entire 100% of the CPU-time (P4 at 2GHz); it only writes @4Mb/s (~14% of the disk's bandwidth) and the only cure is to restart the /etc/rc.d/nfsd; trying to, for example, switch from X11 to a textual console, when this is happening reliably hangs the machine. . 5.2-CURRENT (Dec 14) server, 5.2-RC2 (Jan 10) client: dumps happen normally with rw-mounts, but mounting the FS read-only (so as to prevent core-dumps) leads to a panic on the client... The mounts are regular and default (v3?), except for the ``intr'' flag. No rpc.lock or anything... Any comments? -mi