Date: Tue, 2 Jun 2009 20:57:06 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-current@FreeBSD.org, "O. Hartmann" <ohartman@zedat.fu-berlin.de> Subject: Re: RPCPROG_MNT: RPC: Timed out / receiving NFS error when trying to mount NFS file system after make world Message-ID: <alpine.BSF.2.00.0906022053170.52806@fledge.watson.org> In-Reply-To: <Pine.GSO.4.63.0906021146470.19159@muncher.cs.uoguelph.ca> References: <4A2504AA.1020406@zedat.fu-berlin.de> <Pine.GSO.4.63.0906021030500.6192@muncher.cs.uoguelph.ca> <4A254194.7080807@zedat.fu-berlin.de> <Pine.GSO.4.63.0906021146470.19159@muncher.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Jun 2009, Rick Macklem wrote: >> Mounting via '-o nfsv3,tcp' in addition, everthing works all right again. I >> do not know why udp is invoked automatically by now. >> >> But for short, we always did NFS mounts over tcp AND udp, so for tcp it >> worked again! >> > Hmm, weird. udp mounts work here for me (except NFSv4, where tcp is > required, but you'd only get that if you had used "-o nfsv4" in your mount). > > I'll take another look at mount_nfs.c too (already caught a problem I > introduced in mountd.c). Maybe I unintentionally changed one of the > defaults. (I think the default is supposed to be nfsv3,tcp but I'll look.) I'm running into a similar-sounding but odd problem on a diskless NFS client test box running 8.0, but talking to a server running 7.0: cheetah# mount -o rw -u / [udp] zoo:/zoo/cheetah: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to send If I do a fresh file system mount it works fine: cheetah# mount 192.168.5.1:/zoo /zoo cheetah# mount 192.168.5.1:/zoo/cheetah on / (nfs, read-only) devfs on /dev (devfs, local) /dev/md0 on /var (ufs, local) /dev/md1 on /tmp (ufs, local) 192.168.5.1:/zoo on /zoo (nfs) This is with an approximately 26 May userspace. Robert N M Watson Computer Laboratory University of Cambridge > > For udp to work, nfsd must have the "-u" argument. That might be why it > wouldn't work? (Still doesn't explain why the default was udp and not > tcp.) > > Anyhow, thanks for doing the testing and I'll email again if I find > that I've screwed up the defaults for mount_nfs too. (Is that a > "big pointy hat"?:-) > > rick > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0906022053170.52806>