Linux NFS development
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Weston Andros Adamson <dros@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Getting 'not supported' when trying to mount IPv6 NFS v3 server.
Date: Mon, 21 Oct 2013 16:54:53 -0700	[thread overview]
Message-ID: <5265BECD.1060601@candelatech.com> (raw)
In-Reply-To: <4682F017-7329-4690-B336-233DB50537F0@netapp.com>

On 10/21/2013 04:44 PM, Weston Andros Adamson wrote:
> 
> On Oct 21, 2013, at 5:32 PM, Ben Greear <greearb@candelatech.com> wrote:
> 
>> So, the problem I reported earlier with failing to unmount was fixed
>> by the back-ported patch.
>>
>> Now, another problem is reported by my user.  In this case, they are
>> trying to mount an IPv6 NFS server using NFSv3.  Kernel is 3.9.11+,
>> with patches to support binding mount points to local IP (v4/v6) addresses.
>>
>> Some NFS over IPv6 mounts work fine, but some do not.  A reboot of the
>> NFS client machine did not fix the problem.
>>
>> I have tried to reproduce the problem locally, but so far everything works fine
>> for us.
>>
>> From my own app's logs:
>>
>> # mount -t nfs [4001:1::1:1]:/vol/vol1 /mnt/lf/RDnfse11c0 -o srcaddr=4001:1::1:201,vers=3
>> # requested NFS version or transport protocol is not supported
>>
>> When this problem happens, I do not see any network traffic when trying to mount.
> 
> Did you look for the mount protocol when getting a network trace (filter "rpc" in wireshark).

I saw zero NFS related packets on the wire when hitting this problem.
But, there could have been packets earlier that put it into a funky
state, or a bit less likely, they could have been going out some of the
other virtual interfaces on the system.

> Could you:
> 
>   1) run "rpcdebug -m nfs -s mount" before mounting, post output of dmesg after mount fails.
> 
>   2) add -v to the mount command and post the output

I can try this.

>   3) maybe get rid of srcaddr= option / post info about the ip configuration

I can't easily do this, as the user's setup requires the srcaddr to route properly
to the filer.

I am also going to run a kernel with printks added around all the EOPNOTSUPP
returns that I can find to try to track down what part of the kernel is
complaining.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2013-10-21 23:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 21:32 Getting 'not supported' when trying to mount IPv6 NFS v3 server Ben Greear
2013-10-21 23:44 ` Weston Andros Adamson
2013-10-21 23:54   ` Ben Greear [this message]
2013-10-22  0:04     ` Weston Andros Adamson
2013-10-22  0:20     ` Jim Rees
2013-10-22  3:18       ` Ben Greear
2013-10-22 12:56         ` Weston Andros Adamson
2013-10-22 14:19 ` Michael Richardson
2013-10-22 15:54   ` Ben Greear

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5265BECD.1060601@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=dros@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox