Date: Mon, 19 May 1997 18:40:59 +0200 (SAT) From: John Hay <jhay@zibbi.mikom.csir.co.za> To: jhay@zibbi.mikom.csir.co.za (jhay) Cc: freebsd-stable@freebsd.org Subject: Re: amd and nfs v2 problems Message-ID: <199705191640.SAA05016@zibbi.mikom.csir.co.za> In-Reply-To: From jhay at "May 19, 97 11:02:50 am"
next in thread | raw e-mail | index | archive | help
> Hi, > > I have upgraded our one FreeBSD server from 2.2.1 to 2.2.2 this weekend > and seems to be bitten by nfs that is now v3 by default. I have a amd > setup here and it was working before, but now I'm getting errors and > it isn't mounting properly. The errors are something like this: > > ===== > May 19 10:50:23 zibbi amd[21803]: /net/skeleton: mount: Bad address > May 19 10:50:23 zibbi amd[21803]: /net/skeleton/home: mount: Bad address > ===== > > If I manually mount the servers and force nfs v2, it works. Is there > some way to force amd to use v2 for some hosts? I have tried the "nfsv2" > option in the amd.map file, but it does not seem to help at all. > > If it matters, the two nfs servers I'm trying to mount is running > FreeBSD 2.1.7 and HPUX 9.04. > OK, I did some more testing. If I do a manual nfs mount without forcing it to nfsv2 it also works. So then I tried it with the old 2.2.1 amd and that also works. So it seems to be something that the new amd do. Is there someone actually using amd on 2.2.2 or is the problem just with my setup? John -- John Hay -- John.Hay@mikom.csir.co.za
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705191640.SAA05016>