Linux NFS development
 help / color / mirror / Atom feed
From: Weston Andros Adamson <dros@netapp.com>
To: Ben Greear <greearb@candelatech.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 23:44:55 +0000	[thread overview]
Message-ID: <4682F017-7329-4690-B336-233DB50537F0@netapp.com> (raw)
In-Reply-To: <52659D69.1020609@candelatech.com>


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).

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

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

> 
> 
> I am curious if anyone else has seen errors similar to this?
> 
> 
> Thanks,
> Ben
> 
> -- 
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2013-10-21 23:45 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 [this message]
2013-10-21 23:54   ` Ben Greear
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=4682F017-7329-4690-B336-233DB50537F0@netapp.com \
    --to=dros@netapp.com \
    --cc=greearb@candelatech.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