From owner-freebsd-current Sun Mar 1 07:53:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27295 for freebsd-current-outgoing; Sun, 1 Mar 1998 07:53:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27289 for ; Sun, 1 Mar 1998 07:53:27 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id KAA02555; Sun, 1 Mar 1998 10:53:22 -0500 (EST) (envelope-from toor) Message-Id: <199803011553.KAA02555@dyson.iquest.net> Subject: Re: Lockup in inode/nfsrcv on loopback NFS mount In-Reply-To: from Brian Tao at "Mar 1, 98 10:36:38 am" To: taob@nbc.netcom.ca Date: Sun, 1 Mar 1998 10:53:22 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Tao said: > Could someone with a recent -current (I'm using Feb 28's) try > exporting a filesystem, mounting it via localhost and copying a large > file (a few megabytes will do) to the NFS-mounted filesystem? I've > seen results from only NFS locking up, to all filesystems hanging, to > the entire system freezing. > There has been a historical problem with NFSv3 hanging on localhost filesystems. Is this a possibility? If so, NFSv2 is a short-term answer (if it is fast enough for you.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message