From owner-freebsd-current Mon Jan 27 2:48:18 2003 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 CB1B337B401 for ; Mon, 27 Jan 2003 02:48:16 -0800 (PST) Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2947B43F3F for ; Mon, 27 Jan 2003 02:48:16 -0800 (PST) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by white.imgsrc.co.jp (Postfix) with ESMTP id 56FCA24DCE; Mon, 27 Jan 2003 19:48:15 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by white.imgsrc.co.jp (Postfix) with ESMTP id BD22424D06; Mon, 27 Jan 2003 19:48:12 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by black.imgsrc.co.jp (Postfix) with ESMTP id 96C7F1E4817; Mon, 27 Jan 2003 19:48:12 +0900 (JST) Date: Mon, 27 Jan 2003 19:48:12 +0900 Message-ID: <7mu1fudg2b.wl@black.imgsrc.co.jp> From: Jun Kuriyama To: Martin Blapp Cc: freebsd-current@FreeBSD.org Subject: Re: 4.7-amd cannot mount exports from 5.0-RELEASE In-Reply-To: <20030127111923.R55439@levais.imp.ch> References: <3E2AFC59.40707@gmx.net> <87d6mseeti.wl@ale.imgsrc.co.jp> <3E2BB02C.3040905@gmx.net> <873cnmdqvb.wl@ale.imgsrc.co.jp> <7mznpnc6u2.wl@black.imgsrc.co.jp> <20030127111923.R55439@levais.imp.ch> User-Agent: Wanderlust/2.10.0 (Venus) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-4?Q?Kashiharajing=FE-mae?=) APEL/10.4 Emacs/21.2 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020531 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Mon, 27 Jan 2003 11:21:54 +0100 (CET), Martin Blapp wrote: > There seem to be definitly a problem around. Can you exactly tell > me how you can reproduce it ? Hmm, sorry for my little description. > I tried it too and amd still works. I use on both servers a recent > CURRENT and one has amd running, the other the nfsd and mountd. > > tcp and udp mounts still work fine. So the trigger of this > bug must be elsewhere ... In my environment, server is 5.0-RELEASE and client is HEAD as of Jan 20th. Both have nfsd, rpc.lockd, rpc.statd and nfs client. I'll verify to find the case which is easy to reproduce. -- Jun Kuriyama // IMG SRC, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message