NFS mountd version 3 over TCP
swills at FreeBSD.org
Mon Aug 29 06:41:41 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
On 08/27/11 21:23, Steve Wills wrote:
> On 08/27/11 20:55, Rick Macklem wrote:
>>> I don't know why the nfsd wouldn't be able to bind(2) to port #2049 a
>>> second time for UDP, but someone on the net side might know? (Just in
>>> case it is a problem that has already been fixed, I'd try a newer kernel.)
> Will do, see below.
>>> The new server was broken by r224778 on Aug. 11 and fixed by r224911 on
>>> Aug. 16. (I recall you mentioning Aug. 11?)
> My kernel is from Aug 13, so definitely would fall into that range. I'll
> update and rebuild and see how it goes.
After working around the /dev/stdout issue by booting an old kernel and
doing a buildworld from there, I was able to update my kernel to todays
sources. ESXi is now able to mount the nfs share. However, when I
attempt to start a VM, it reports:
Failed to power on VM.
Unable to retrieve the current working directory: 0 (Input/output
error). Check if the directory has been deleted or unmounted.
FILE: File_Cwd: getcwd() failed: Input/output error
I have tcpdump output available here:
if that helps.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the freebsd-current