Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Jun 2009 11:53:37 -0400 (EDT)
From:      Rick Macklem <rmacklem@uoguelph.ca>
To:        "O. Hartmann" <ohartman@zedat.fu-berlin.de>
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: RPCPROG_MNT: RPC: Timed out / receiving NFS error when trying to mount NFS file system after make world
Message-ID:  <Pine.GSO.4.63.0906021146470.19159@muncher.cs.uoguelph.ca>
In-Reply-To: <4A254194.7080807@zedat.fu-berlin.de>
References:  <4A2504AA.1020406@zedat.fu-berlin.de> <Pine.GSO.4.63.0906021030500.6192@muncher.cs.uoguelph.ca> <4A254194.7080807@zedat.fu-berlin.de>

next in thread | previous in thread | raw e-mail | index | archive | help


On Tue, 2 Jun 2009, O. Hartmann 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.)

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0906021146470.19159>