Re: NFS mountd version 3 over TCP

2011-08-29 Thread Steve Wills
-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

Re: NFS mountd version 3 over TCP

2011-08-29 Thread Rick Macklem
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

Re: NFS mountd version 3 over TCP

2011-08-29 Thread Steve Wills
-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

Re: NFS mountd version 3 over TCP

2011-08-27 Thread Rick Macklem
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

Re: NFS mountd version 3 over TCP

2011-08-27 Thread Steve Wills
-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

Re: NFS mountd version 3 over TCP

2011-08-27 Thread Rick Macklem
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

Re: NFS mountd version 3 over TCP

2011-08-27 Thread Rick Macklem
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

Re: NFS mountd version 3 over TCP

2011-08-27 Thread Steve Wills
-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

Re: NFS mountd version 3 over TCP

2011-08-26 Thread Steve Wills
-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

Re: NFS mountd version 3 over TCP

2011-08-26 Thread Steve Wills
-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