NFS mountd version 3 over TCP

Rick Macklem rmacklem at
Sat Aug 27 22:07:28 UTC 2011

Steve Wills wrote:
> Hash: SHA1
> On 08/27/11 09:00, Rick Macklem wrote:
> >> This line indicates that mountd over tcp is registered for v3,
> >> so I suspect the error message is misleading??
> Forgot to reply to this part, and I should have been more clear
> earlier.
> When I used the default nfsd flags, it failed to startup, or exited
> immediately on startup (not sure which).
I have no idea w.r.t. this one. The failure is the bind(2) syscall failing
for port #2049 over UDP, but I have no idea why? (Others aren't seeing this,
as far as I know.)

 When I removed -u flag, it
> started up and that message was replaced with the one about fsinfo
> timeout.
> I can get the exact error message and tcpdump if you like.
Both the message and a tcpdump (binary capture of traffic between the
two hosts) would be useful. A tcpdump command like this done on the FreeBSD
server: tcpdump -s 0 -w <file> host <client>

You can just email me <file> as an attachment and I'll take a look at it.
> I
> then added -o flag to nfsd (didn't put -u back) and then things seemed
> to work OK.
> Steve
> Version: GnuPG v2.0.17 (FreeBSD)
> +O31ScAk+weud90cEjf/N9PwW5PfSJYHMO03hliMVGuOphkwYnpN2AStExzScfmm
> nCFLz5UpzeKjznzirSOSNCGqwAyN3aPrghlyqNNi5eSkM9s0BdJgKBd+H9oSk7JE
> 7rf83Q2kPdqfvwhvRNpImC5oEXkZpExmitoIhESdnI/asr5OBwHIh8HthgIgMx+o
> 0t7v+togz0dT2jR7D+U1QbKhH5QP8pamjpP80D4TsO8P9pGt/PUuSBQAwDfQ3pjf
> Tjnc2t9YMQ+hw3zqYTRrNCNMvaH7PlyAW0LvuW1Nhk8mus6HFxP1St/hgko+Y+8=
> =Pdq4

More information about the freebsd-current mailing list