Re: NFS mountd version 3 over TCP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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. and FILE: File_Cwd: getcwd() failed: Input/output error I have tcpdump output available here: http://people.freebsd.org/~swills/nfs2.pcap if that helps. Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWzShAAoJEPXPYrMgexuhxo0H/0ALErvMrpcxtkuUv07ipj0O Z8p3YkMFkckSy6s0QCAOCVgjbqZptCkKg96vMehG3nI5o2HtA43h5y6UNvMi1FWE WOiIFbzXkgfn1pubv2YyFwaDK1aFXMswwYaCHSP7a+K8fpjDOiR5ZnhhyXcb7k1X YmURkSEbLbngLdIfywPATSiby9PyFVqyMjhU3yW/Y8QLueEjK4xq5RsbmU1Qmv2B bjA11x9birNvc//iBp6zTqBP752soqK+M9aXrjjm9GzhN0UeKdXseWt9zd3mu2qs cfPUqz7DSATQNxwfpqIGnE4naYzPyKPbDbv6k5lKDjmmHn2O7VzXQXimjE6sT3o= =Dpjc -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NFS mountd version 3 over TCP
Steve Wills wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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. and FILE: File_Cwd: getcwd() failed: Input/output error I have tcpdump output available here: http://people.freebsd.org/~swills/nfs2.pcap if that helps. I think it did. Lookup of .. was failing. I think that was because ni_strictrelative (added for capabilities) wasn't initialized and happened to be non-zero. Please try this patch and let us know if it helps: --- fs/nfsserver/nfs_nfsdport.c.sav 2011-08-29 11:05:00.0 -0400 +++ fs/nfsserver/nfs_nfsdport.c 2011-08-29 11:29:43.0 -0400 @@ -282,6 +282,10 @@ nfsvno_namei(struct nfsrv_descript *nd, *retdirp = NULL; cnp-cn_nameptr = cnp-cn_pnbuf; + /* Initialize new fields for capabilities. */ + ndp-ni_strictrelative = 0; + ndp-ni_rightsneeded = 0; + ndp-ni_baserights = 0; /* * Extract and set starting directory. */ It's also at (in case white space gets munged) http://people.freebsd.org/~rmacklem/dotdot.patch Thanks for reporting this, I'm not sure when these fields not being initialized would have been noticed otherwise, rick Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWzShAAoJEPXPYrMgexuhxo0H/0ALErvMrpcxtkuUv07ipj0O Z8p3YkMFkckSy6s0QCAOCVgjbqZptCkKg96vMehG3nI5o2HtA43h5y6UNvMi1FWE WOiIFbzXkgfn1pubv2YyFwaDK1aFXMswwYaCHSP7a+K8fpjDOiR5ZnhhyXcb7k1X YmURkSEbLbngLdIfywPATSiby9PyFVqyMjhU3yW/Y8QLueEjK4xq5RsbmU1Qmv2B bjA11x9birNvc//iBp6zTqBP752soqK+M9aXrjjm9GzhN0UeKdXseWt9zd3mu2qs cfPUqz7DSATQNxwfpqIGnE4naYzPyKPbDbv6k5lKDjmmHn2O7VzXQXimjE6sT3o= =Dpjc -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NFS mountd version 3 over TCP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 08/29/11 11:47, Rick Macklem wrote: I think it did. Lookup of .. was failing. I think that was because ni_strictrelative (added for capabilities) wasn't initialized and happened to be non-zero. Please try this patch and let us know if it helps: That fixed it, thanks! Thanks for reporting this, I'm not sure when these fields not being initialized would have been noticed otherwise, rick No problem, thanks for the quick response. If I see any other issues I'll be sure to report them. Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOXBlDAAoJEPXPYrMgexuhWzQH/AjTSRYzw93cn78BXwOpUVKJ nS22ZH/fFdW6Jvaa/Ph1xHj6P04zjOlIrxTEIEnQvDlWKJkdnG/JwIuvOKFHmyiu VpFBDReTNSPO3wN2t3pAOz89Kfs3mVkY1AvFly5RJ+CmZAzo/zafamS0UHICIm49 wSDb/KDo+hkEF+5Iluqsbm453wU0PiDjmPhlkvuFtGkn7kuuoU2r+inBFT5AzYlO 1iX79uKRJEywcaVFBbL4QiEVG6w/SWI+mUIy+TZmfAtaQGSQMJ2sEpGlcYSSzZ8E 4BLf9C2BPE+IWR8ssw1eF99+W39yCszpaauXhgwX1Tjrv/Ae0PBDONd4H1ejekQ= =T0ct -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NFS mountd version 3 over TCP
Steve Wills wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/26/11 22:16, Steve Wills wrote:
On 08/26/11 21:41, Steve Wills wrote:
Hi,
I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi
4.1.0.
When I attempt the mount, it logs this message:
The NFS server does not support MOUNT version 3 over TCP
Have I configured something wrong and if so what? Or is this
something
related to the new NFS code?
I guess a little more info would be helpful...
rc.conf has:
nfs_server_enable=YES
rpcbind_enable=YES
mountd_enable=YES
rpc_statd_enable=YES
rpc_lockd_enable=YES
/etc/exports contains, amongst others:
/boxy/vmware -alldirs -maproot=0:0 -network 10.0.1 -mask
255.255.255.0
rpcinfo shows:
program version netid address service owner
10 4 tcp 0.0.0.0.0.111 rpcbind superuser
10 3 tcp 0.0.0.0.0.111 rpcbind superuser
10 2 tcp 0.0.0.0.0.111 rpcbind superuser
10 4 udp 0.0.0.0.0.111 rpcbind superuser
10 3 udp 0.0.0.0.0.111 rpcbind superuser
10 2 udp 0.0.0.0.0.111 rpcbind superuser
10 4 tcp6 ::.0.111 rpcbind superuser
10 3 tcp6 ::.0.111 rpcbind superuser
10 4 udp6 ::.0.111 rpcbind superuser
10 3 udp6 ::.0.111 rpcbind superuser
10 4 local /var/run/rpcbind.sock rpcbind superuser
10 3 local /var/run/rpcbind.sock rpcbind superuser
10 2 local /var/run/rpcbind.sock rpcbind superuser
15 1 udp6 ::.2.224 mountd superuser
15 3 udp6 ::.2.224 mountd superuser
15 1 tcp6 ::.2.224 mountd superuser
15 3 tcp6 ::.2.224 mountd superuser
15 1 udp 0.0.0.0.2.224 mountd superuser
15 3 udp 0.0.0.0.2.224 mountd superuser
15 1 tcp 0.0.0.0.2.224 mountd superuser
15 3 tcp 0.0.0.0.2.224 mountd superuser
This line indicates that mountd over tcp is registered for v3,
so I suspect the error message is misleading??
As you might guess, this rpcinfo output indicates nfsd wasn't running.
I
am seeing this:
can't bind udp addr *: Address already in use
Hmm, this should only happen if the nfsd is already running (or was
recently running), since nothing else binds to port #2049 normally.
(If something else grabbed port#2049 for udp, then that would explain
this.) I assume the message was from nfsd?
in syslog. Setting this:
nfs_server_flags=-t -n 4
allowed it to startup, but it then timed out an fsinfo call. Adding -o
to the nfs_server_flags to use the old nfs server allowed vmware to
mount. FWIW, I can't find any reason for the udp message above,
nothing
seems to be using it that I can find. Ideas? tcpdumps are available if
anyone want them.
Could you make sure you have this patch, which was committed by zkirsch
as r224637. It was a fix they needed for a customer having difficulties
mounting via VMware. (Our discussion about it agreed that the VMware
client was broken for this case, but the patch fixed the problem.)
If you didn't already have this patch, please test it (ie. apply it and
take -o off the nfsd flags) and let us know if it fixed your problem?
--- head/sys/fs/nfsserver/nfs_nfsdserv.c2011/07/31 20:06:11 224554
+++ head/sys/fs/nfsserver/nfs_nfsdserv.c2011/08/03 18:50:19 224637
@@ -620,7 +620,7 @@
vnode_t vp, NFSPROC_T *p, struct nfsexstuff *exp)
{
u_int32_t *tl;
- int error = 0, cnt, len, getret = 1, reqlen, eof = 0;
+ int error = 0, cnt, getret = 1, reqlen, eof = 0;
mbuf_t m2, m3;
struct nfsvattr nva;
off_t off = 0x0;
@@ -714,11 +714,11 @@
eof = 1;
} else if (reqlen == 0)
cnt = 0;
- else if ((off + reqlen) nva.na_size)
+ else if ((off + reqlen) = nva.na_size) {
cnt = nva.na_size - off;
- else
+ eof = 1;
+ } else
cnt = reqlen;
- len = NFSM_RNDUP(cnt);
m3 = NULL;
if (cnt 0) {
nd-nd_repstat = nfsvno_read(vp, off, cnt, nd-nd_cred, p,
@@ -748,7 +748,7 @@
*tl++ = txdr_unsigned(cnt);
} else
NFSM_BUILD(tl, u_int32_t *, 2 * NFSX_UNSIGNED);
- if (len reqlen || eof)
+ if (eof)
*tl++ = newnfs_true;
else
*tl++ = newnfs_false;
Steve
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (FreeBSD)
iQEcBAEBAgAGBQJOWF6PAAoJEPXPYrMgexuhHPYIAJ6SVxtORDbesvU35ktAS/id
5iWyTWO3CTHXT42uP4IZBT1o2AWFu6e9wUX84YEZyujMln0E++8hZccaa8zQBJhr
febHkZxqPdQOo/mpg1ci5J70Hs1UBV9cxU3uOA83vxunOM6xwA0B+4krfflj/k7P
cPtpztmuepQQ8/S5hB5ajnfM/gFOh1f2uPwWTj2/5NSWMoVfN3f0539bh05XKfRa
4X7XKxN/J4HBRGaNjnL8IWu86AW60H9Q3gdisdtT0k9sK4X3DswmiRMlMt4M4rS8
oX0vrgruTiKZf+bsraYvhuo4JyselXMicTnW7rUOVx8jiNVVk1nymSVF1XDUOrw=
=MeJv
-END PGP SIGNATURE-
Re: NFS mountd version 3 over TCP
-BEGIN PGP SIGNED MESSAGE- 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). 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. I then added -o flag to nfsd (didn't put -u back) and then things seemed to work OK. Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWPPUAAoJEPXPYrMgexuhrLIH/jpRbAaKde9qi3xzsiIaZsuI +O31ScAk+weud90cEjf/N9PwW5PfSJYHMO03hliMVGuOphkwYnpN2AStExzScfmm nCFLz5UpzeKjznzirSOSNCGqwAyN3aPrghlyqNNi5eSkM9s0BdJgKBd+H9oSk7JE 7rf83Q2kPdqfvwhvRNpImC5oEXkZpExmitoIhESdnI/asr5OBwHIh8HthgIgMx+o 0t7v+togz0dT2jR7D+U1QbKhH5QP8pamjpP80D4TsO8P9pGt/PUuSBQAwDfQ3pjf Tjnc2t9YMQ+hw3zqYTRrNCNMvaH7PlyAW0LvuW1Nhk8mus6HFxP1St/hgko+Y+8= =Pdq4 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NFS mountd version 3 over TCP
Steve Wills wrote: -BEGIN PGP SIGNED MESSAGE- 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 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWPPUAAoJEPXPYrMgexuhrLIH/jpRbAaKde9qi3xzsiIaZsuI +O31ScAk+weud90cEjf/N9PwW5PfSJYHMO03hliMVGuOphkwYnpN2AStExzScfmm nCFLz5UpzeKjznzirSOSNCGqwAyN3aPrghlyqNNi5eSkM9s0BdJgKBd+H9oSk7JE 7rf83Q2kPdqfvwhvRNpImC5oEXkZpExmitoIhESdnI/asr5OBwHIh8HthgIgMx+o 0t7v+togz0dT2jR7D+U1QbKhH5QP8pamjpP80D4TsO8P9pGt/PUuSBQAwDfQ3pjf Tjnc2t9YMQ+hw3zqYTRrNCNMvaH7PlyAW0LvuW1Nhk8mus6HFxP1St/hgko+Y+8= =Pdq4 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NFS mountd version 3 over TCP
Steve Wills wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/26/11 22:16, Steve Wills wrote:
On 08/26/11 21:41, Steve Wills wrote:
Hi,
I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi
4.1.0.
When I attempt the mount, it logs this message:
The NFS server does not support MOUNT version 3 over TCP
Have I configured something wrong and if so what? Or is this
something
related to the new NFS code?
I guess a little more info would be helpful...
rc.conf has:
nfs_server_enable=YES
rpcbind_enable=YES
mountd_enable=YES
rpc_statd_enable=YES
rpc_lockd_enable=YES
/etc/exports contains, amongst others:
/boxy/vmware -alldirs -maproot=0:0 -network 10.0.1 -mask
255.255.255.0
rpcinfo shows:
program version netid address service owner
10 4 tcp 0.0.0.0.0.111 rpcbind superuser
10 3 tcp 0.0.0.0.0.111 rpcbind superuser
10 2 tcp 0.0.0.0.0.111 rpcbind superuser
10 4 udp 0.0.0.0.0.111 rpcbind superuser
10 3 udp 0.0.0.0.0.111 rpcbind superuser
10 2 udp 0.0.0.0.0.111 rpcbind superuser
10 4 tcp6 ::.0.111 rpcbind superuser
10 3 tcp6 ::.0.111 rpcbind superuser
10 4 udp6 ::.0.111 rpcbind superuser
10 3 udp6 ::.0.111 rpcbind superuser
10 4 local /var/run/rpcbind.sock rpcbind superuser
10 3 local /var/run/rpcbind.sock rpcbind superuser
10 2 local /var/run/rpcbind.sock rpcbind superuser
15 1 udp6 ::.2.224 mountd superuser
15 3 udp6 ::.2.224 mountd superuser
15 1 tcp6 ::.2.224 mountd superuser
15 3 tcp6 ::.2.224 mountd superuser
15 1 udp 0.0.0.0.2.224 mountd superuser
15 3 udp 0.0.0.0.2.224 mountd superuser
15 1 tcp 0.0.0.0.2.224 mountd superuser
15 3 tcp 0.0.0.0.2.224 mountd superuser
As you might guess, this rpcinfo output indicates nfsd wasn't running.
I
am seeing this:
can't bind udp addr *: Address already in use
in syslog. Setting this:
nfs_server_flags=-t -n 4
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.)
allowed it to startup, but it then timed out an fsinfo call. Adding -o
to the nfs_server_flags to use the old nfs server allowed vmware to
mount. FWIW, I can't find any reason for the udp message above,
nothing
seems to be using it that I can find. Ideas? tcpdumps are available if
anyone want them.
The new server was broken by r224778 on Aug. 11 and fixed by r224911 on
Aug. 16. (I recall you mentioning Aug. 11?)
Here's the r224911 patch:
--- head/sys/fs/nfsserver/nfs_nfsdport.c2011/08/11 12:30:23 224778
+++ head/sys/fs/nfsserver/nfs_nfsdport.c2011/08/16 14:23:16 224911
@@ -3036,7 +3036,6 @@
*/
if ((error = fget(td, sockarg.sock, CAP_SOCK_ALL, fp)) != 0)
goto out;
- return (error);
if (fp-f_type != DTYPE_SOCKET) {
fdrop(fp, td);
error = EPERM;
I suspect this is what caused the fsinfo RPC to not reply.
Steve
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (FreeBSD)
iQEcBAEBAgAGBQJOWF6PAAoJEPXPYrMgexuhHPYIAJ6SVxtORDbesvU35ktAS/id
5iWyTWO3CTHXT42uP4IZBT1o2AWFu6e9wUX84YEZyujMln0E++8hZccaa8zQBJhr
febHkZxqPdQOo/mpg1ci5J70Hs1UBV9cxU3uOA83vxunOM6xwA0B+4krfflj/k7P
cPtpztmuepQQ8/S5hB5ajnfM/gFOh1f2uPwWTj2/5NSWMoVfN3f0539bh05XKfRa
4X7XKxN/J4HBRGaNjnL8IWu86AW60H9Q3gdisdtT0k9sK4X3DswmiRMlMt4M4rS8
oX0vrgruTiKZf+bsraYvhuo4JyselXMicTnW7rUOVx8jiNVVk1nymSVF1XDUOrw=
=MeJv
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NFS mountd version 3 over TCP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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. Thanks! Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWZinAAoJEPXPYrMgexuhgp0H/1Dl9Bica8wbx5wLkkaPg5KM Rf53qdAgi/TarcMxufN+ujqx1EBu02hsSfB0vx8B0EZ9Ta1qWA/b2aL8SHJsXZFB gWPyr6sLINLcoaKGJ6Esp4QcIaU0PHOn4OhSGSMaZKYuMlXGsqJyJ3Wn6D46/4Re CbxioTfNT3c85x/khSE3nOCKsxKddKmM+VtuOloNRji969QlYH/1ZWItxbg6Tr1m hkT6v6hAM+EnvuLxlOJMTIegeec+WilIYSyP/FcuB2fcov1rdJSOOqOAUBHiBkRc uz3ADLr1QhwVue7sSA2PNDo3jQhtA7HFQKrEnIAW1xQFKuuapdgxr/wSDu2+T30= =5j1q -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NFS mountd version 3 over TCP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/26/11 21:41, Steve Wills wrote: Hi, I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi 4.1.0. When I attempt the mount, it logs this message: The NFS server does not support MOUNT version 3 over TCP Have I configured something wrong and if so what? Or is this something related to the new NFS code? I guess a little more info would be helpful... rc.conf has: nfs_server_enable=YES rpcbind_enable=YES mountd_enable=YES rpc_statd_enable=YES rpc_lockd_enable=YES /etc/exports contains, amongst others: /boxy/vmware -alldirs -maproot=0:0 -network 10.0.1 -mask 255.255.255.0 rpcinfo shows: program version netid addressserviceowner 104tcp 0.0.0.0.0.111 rpcbindsuperuser 103tcp 0.0.0.0.0.111 rpcbindsuperuser 102tcp 0.0.0.0.0.111 rpcbindsuperuser 104udp 0.0.0.0.0.111 rpcbindsuperuser 103udp 0.0.0.0.0.111 rpcbindsuperuser 102udp 0.0.0.0.0.111 rpcbindsuperuser 104tcp6 ::.0.111 rpcbindsuperuser 103tcp6 ::.0.111 rpcbindsuperuser 104udp6 ::.0.111 rpcbindsuperuser 103udp6 ::.0.111 rpcbindsuperuser 104local /var/run/rpcbind.sock rpcbindsuperuser 103local /var/run/rpcbind.sock rpcbindsuperuser 102local /var/run/rpcbind.sock rpcbindsuperuser 151udp6 ::.2.224 mountd superuser 153udp6 ::.2.224 mountd superuser 151tcp6 ::.2.224 mountd superuser 153tcp6 ::.2.224 mountd superuser 151udp 0.0.0.0.2.224 mountd superuser 153udp 0.0.0.0.2.224 mountd superuser 151tcp 0.0.0.0.2.224 mountd superuser 153tcp 0.0.0.0.2.224 mountd superuser tcpdump here: http://people.freebsd.org/~swills/nfs_debug.pcap Suggestions appreciated, thanks! Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWFOLAAoJEPXPYrMgexuhCvoH/1ky5qXxfQhgTdtYEDbCsfo4 J3xiFG9es+ajpNa1LtqlaMBrvs5fxfv0F7bzklOvUKmsVE4FPuFrcOd6IvIwTw+T U63UFocls3ZufNH+VjzxkFc5jfQ8hTDWXjKPfGMUxrCekt4pcEX4uze+I3YV/WRR IFLTkfUCLvgEJSHn39Yl7ZmHud6kJaUUQv5ne8vWgd8KRNt4IWQqvqltYZDvwY1f 8ajYxJDwKOkVRMhRwh+4O0Fgs3Owar1W0JyNzmJ+Se9/QIVzTwQS6Q4l3jQjfSrU YvRpMFQrb/ChZGZnH//FrXWhHK3TPg++XcRe1PGdY6KB+Fh1gjz+DRzbf5CzYBo= =dp9s -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NFS mountd version 3 over TCP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/26/11 22:16, Steve Wills wrote: On 08/26/11 21:41, Steve Wills wrote: Hi, I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi 4.1.0. When I attempt the mount, it logs this message: The NFS server does not support MOUNT version 3 over TCP Have I configured something wrong and if so what? Or is this something related to the new NFS code? I guess a little more info would be helpful... rc.conf has: nfs_server_enable=YES rpcbind_enable=YES mountd_enable=YES rpc_statd_enable=YES rpc_lockd_enable=YES /etc/exports contains, amongst others: /boxy/vmware -alldirs -maproot=0:0 -network 10.0.1 -mask 255.255.255.0 rpcinfo shows: program version netid addressserviceowner 104tcp 0.0.0.0.0.111 rpcbindsuperuser 103tcp 0.0.0.0.0.111 rpcbindsuperuser 102tcp 0.0.0.0.0.111 rpcbindsuperuser 104udp 0.0.0.0.0.111 rpcbindsuperuser 103udp 0.0.0.0.0.111 rpcbindsuperuser 102udp 0.0.0.0.0.111 rpcbindsuperuser 104tcp6 ::.0.111 rpcbindsuperuser 103tcp6 ::.0.111 rpcbindsuperuser 104udp6 ::.0.111 rpcbindsuperuser 103udp6 ::.0.111 rpcbindsuperuser 104local /var/run/rpcbind.sock rpcbindsuperuser 103local /var/run/rpcbind.sock rpcbindsuperuser 102local /var/run/rpcbind.sock rpcbindsuperuser 151udp6 ::.2.224 mountd superuser 153udp6 ::.2.224 mountd superuser 151tcp6 ::.2.224 mountd superuser 153tcp6 ::.2.224 mountd superuser 151udp 0.0.0.0.2.224 mountd superuser 153udp 0.0.0.0.2.224 mountd superuser 151tcp 0.0.0.0.2.224 mountd superuser 153tcp 0.0.0.0.2.224 mountd superuser As you might guess, this rpcinfo output indicates nfsd wasn't running. I am seeing this: can't bind udp addr *: Address already in use in syslog. Setting this: nfs_server_flags=-t -n 4 allowed it to startup, but it then timed out an fsinfo call. Adding -o to the nfs_server_flags to use the old nfs server allowed vmware to mount. FWIW, I can't find any reason for the udp message above, nothing seems to be using it that I can find. Ideas? tcpdumps are available if anyone want them. Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWF6PAAoJEPXPYrMgexuhHPYIAJ6SVxtORDbesvU35ktAS/id 5iWyTWO3CTHXT42uP4IZBT1o2AWFu6e9wUX84YEZyujMln0E++8hZccaa8zQBJhr febHkZxqPdQOo/mpg1ci5J70Hs1UBV9cxU3uOA83vxunOM6xwA0B+4krfflj/k7P cPtpztmuepQQ8/S5hB5ajnfM/gFOh1f2uPwWTj2/5NSWMoVfN3f0539bh05XKfRa 4X7XKxN/J4HBRGaNjnL8IWu86AW60H9Q3gdisdtT0k9sK4X3DswmiRMlMt4M4rS8 oX0vrgruTiKZf+bsraYvhuo4JyselXMicTnW7rUOVx8jiNVVk1nymSVF1XDUOrw= =MeJv -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
