[ewg] Re: [Bug 1856] NFS unable to register lockd RPC for IPv6

Jon Mason jon at opengridcomputing.com
Thu Dec 17 10:23:20 PST 2009


On Thu, Dec 17, 2009 at 09:37:18AM -0800, Jeff Becker wrote:
> Hi all. I spent some time this week looking into this bug.
> 
> When NFS modules are probed, the following error occurs:
> svc: failed to register lockdv1 (errno 97).
> 
> Initial debug shows that the IPv4 lockd RPC services are started without issue,
> but all IPv6 lockd's fail.  
> 
> I see this on SLES10sp2 and all RHEL5's (even running the 2.6.30 kernel), but
> this issue is not seen on SLES11.  I believe this is an issue with IPv6 support
> in the nfs-utils, but more investigation is needed.
> 
> 
> The problem is that IPV6 support in NFS requires a modern portmapper
> that supports protocol 4 (rpcinfo shows what protocol portmapper
> supports). Jon Mason confirmed that RHEL5.2, RHEL5.3, RHEL5.4, and
> SLES10sp2 all only have portmap v2 support as part of the distro.
> 
> So the question is: Do we need IPV6 support for NFS in the backports?
> Neither Jon nor I think so. Also, people are always free to try a more
> modern portmapper if they like. Neil Brown maintains it at:
> 
> http://neil.brown.name/portmap/
> 
> Not sure about rpms though.
> 
> Thoughts? Can I close the bug as "wont fix" ?

I would document the behavior in the OFED NFSRDMA docs and leave it up
to the customer if they want to try it out.  It is also worth noting
that (to my knowledge) no IPv6 tests have been performed on the
backports.  So, there is a redflag on using IPv6 at all.

Thanks,
Jon

> 
> Thanks.
> 
> -jeff



More information about the ewg mailing list