From owner-freebsd-bugs Wed Jun 4 12:00:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA20913 for bugs-outgoing; Wed, 4 Jun 1997 12:00:02 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA20894; Wed, 4 Jun 1997 12:00:01 -0700 (PDT) Date: Wed, 4 Jun 1997 12:00:01 -0700 (PDT) Message-Id: <199706041900.MAA20894@hub.freebsd.org> To: freebsd-bugs Cc: From: jsin@broadcom.com (John Sin) Subject: Re: kern/3771: bug report for 2.2.2-RELEASE Reply-To: jsin@broadcom.com (John Sin) Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3771; it has been noted by GNATS. From: jsin@broadcom.com (John Sin) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/3771: bug report for 2.2.2-RELEASE Date: Wed, 4 Jun 1997 11:57:20 -0700 >Chris Timmons has pointed out in private mail that this looks like >it might be caused by a more general problem with the loopback >interface that I and others have noticed. Could you please try >the same test again, but using your real host name instead of >"localhost" for the mount? The problem occurs with real host name as well as "localhost". I used "localhost" in the example in an attempt to isolate this problem from other network related issues. >I remember a comment of Doug Rabson that this was a known problem >with our NFSv3 implementation. That seems correct. When I mount the filesystem with NFSv2 -- as in mount -t nfs -o -2 localhost:/ /mnt this problem went away. So at least now I have a workaround! Hopefully this will be fixed soon. Thanks for your help!