Date: Mon, 27 Jan 2003 19:48:12 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Martin Blapp <mb@imp.ch> Cc: freebsd-current@FreeBSD.org Subject: Re: 4.7-amd cannot mount exports from 5.0-RELEASE Message-ID: <7mu1fudg2b.wl@black.imgsrc.co.jp> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <kuriyama@imgsrc.co.jp> // IMG SRC, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mu1fudg2b.wl>