> On Wed, Sep 06, 2017 at 01:47:42PM -0700, Frank Filz wrote: > > > On Wed, Sep 06, 2017 at 12:27:38PM -0700, Frank Filz wrote: > > > > > On Wed, Sep 06, 2017 at 10:18:36AM -0400, Daniel Gryniewicz wrote: > > > > > > On 09/06/2017 09:09 AM, William Allen Simpson wrote: > > > > > > >On 9/5/17 10:44 AM, Daniel Gryniewicz wrote: > > > > > > >>I'm stumped, then. It all looks fine to me. > > > > > > >> > > > > > > >I think you'll find that things work better by switching to TCP. > > > > > > > > > > > > > >The UDP client code (clnt_dg) is badly bugged in general. > > > > > > >That needs re-writing, but UDP hasn't been a priority. > > > > > > > > > > > > > >There were unlocked critical regions fixes in ganesha 2.5. > > > > > > > > > > > > > >In 2.6, we're planning on re-doing the entire call interface > > > > > > >to use async callbacks. There's an XXX in clnt_vc circa 2012 > > mentioning it. > > > > > > > > > > > > > > > > > > Switching to TCP may not be an option, > > > > > > > > > > Whatever you need to do for this bug, eventually I suspect you > > > > > want to > > > > drop > > > > > support for UDP. > > > > > > > > Do we genuinely not have any supported clients out there that will > > > > end up using UDP? Until we do, I think we need to continue to > > > > support UDP as best we can. > > > > > > I haven't heard of a distro with a client that supports only UDP. > > > Or even > > that > > > defaults to UDP. > > > > > > I kind of doubt there's anything at all out there that only supports > > UDP--if > > > there is, my bet would be odd one-off userspace clients or old > > > embedded devices? > > > > > > So if you're seeing UDP it's probably because they explicitly asked > > > for it > > on > > > the mount commandline. > > > > I know at one time, some of the NFS v3 mount activity would wind up on > > UDP even when TCP was specified for mount. Hopefully that has been > > gone away long enough it doesn't remain on any supported clients > anymore. > > I'm just thinking about the main NFS protocol, I don't know what the deal is > with the sideband protocols. > > But are any of those sideband protocols actually being handled by ntirpc > anyway?
Ganesha uses ntirpc for NFS, MOUNTD, RQUOTA, and NLM (It does not support the non-standardized POSIX ACL sideband protocol for NFS 3). There has been discussion of Ganesha bringing rpc.statd inside Ganesha, I don't know if any clients use UDP for NSM communications. Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
