Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Sep 2009 16:48:21 -0400 (EDT)
From:      Rick Macklem <rmacklem@uoguelph.ca>
To:        Doug Poland <doug@polands.org>
Cc:        freebsd-stable@freebsd.org, FreeBSD Current <current@freebsd.org>
Subject:   RE: NFS issues on 8.0-BETA4
Message-ID:  <Pine.GSO.4.63.0909111641240.10263@muncher.cs.uoguelph.ca>
In-Reply-To: <Pine.GSO.4.63.0909111621420.6191@muncher.cs.uoguelph.ca>
References:  <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> <B583FBF374231F4A89607B4D08578A4305454467@bcs-mail03.internal.cacheflow.com> <Pine.GSO.4.63.0909111621420.6191@muncher.cs.uoguelph.ca>

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


On Fri, 11 Sep 2009, Rick Macklem wrote:

>
>
>>> 
>>> I cannot sucessfully mount exports from the NFSv3 server on the
>>> 8.0-BETA4 client.  All works well with 7.2 clients.
>>> 
>>> The strange thing is, the directory in which I mount the nfs
>>> filesystem disappears, and I get an error when I attempt to access the
>>> directory.
>>> 
I just took another glance at your email and see you have your server
configured for UDP only, so that explains it.

As noted in the last posting, the current mount_nfs.c switches to
TCP for NFS by default, so...
- add "udp" to your mount options
OR
- add "-t" to your nfs_server_flags

and I think things will work better.

I vaguely recall posting w.r.t. this uses UDP for the mount protocol
and then TCP for NFS by default and didn't really get any responses.
(I'm new to this and probably posted to freebsd-fs or freebsd-arch.)
At that time, I didn't realize the change was post FreeBSD7, so I
didn't do anything more about it.

Good luck with it and let us know how it goes, rick




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