From owner-freebsd-current Sun Mar 1 15:19:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21200 for freebsd-current-outgoing; Sun, 1 Mar 1998 15:19:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21132; Sun, 1 Mar 1998 15:19:53 -0800 (PST) (envelope-from taob@tor-adm1.nbc.netcom.ca) Received: (from taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) id SAA02857; Sun, 1 Mar 1998 18:19:50 -0500 (EST) Date: Sun, 1 Mar 1998 18:19:50 -0500 (EST) From: Brian Tao X-Sender: taob@tor-adm1 To: "John S. Dyson" cc: freebsd-current@FreeBSD.ORG Subject: Re: Lockup in inode/nfsrcv on loopback NFS mount In-Reply-To: <199803011553.KAA02555@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Mar 1998, John S. Dyson wrote: > > 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.) Yep, NFSv2 works, but it creeps along very slowly. A dd never seems to climb above about 400K/sec on a P100, regardless of the block size. I notice a lot of hard drive chatter during any sustained write operation. Anyway, I don't actually need loopback NFS mounts... it was something I tried when tracking down another problem. Is it specifically a problem with the lo interface? Can it be avoided by somehow going through an Ethernet driver? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message