From: Ben Greear <greearb@candelatech.com>
To: Michael Richardson <mcr@sandelman.ca>
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: Tue, 22 Oct 2013 08:54:39 -0700 [thread overview]
Message-ID: <52669FBF.9040808@candelatech.com> (raw)
In-Reply-To: <357.1382451554@obiwan.sandelman.ca>
On 10/22/2013 07:19 AM, Michael Richardson wrote:
> Ben Greear <greearb@candelatech.com> wrote:
> > 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.
>
> That sounds like the error that one would get when *mount* was compiled with
> the v6-incompatible sunrpc library rather than tirpc.
It works sometimes on the problem system, and it always (so far) works in our lab.
We tried NFSv3 over IPv4, NFSv4 over IPv4, NFSv3 over IPv6 and NFSv4 over IPv6.
We are using the standard 'mount' that comes with the OS (Fedora 14, in this case),
but we are re-compiling the mount.nfs binary, so perhaps there is still some
problem in how we compile it...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-10-22 15: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
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 [this message]
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=52669FBF.9040808@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mcr@sandelman.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.