From: Rajesham Gajjela <rajeshamg@yahoo.com>
To: linux-nfs@vger.kernel.org
Cc: aime.le-rouzic@bull.net,
aurelien.charbon-Z51IpKcfGtLk1uMJSBkQmQ@public.gmane.org,
gilles.quillard@bull.net
Subject: nfs over ipv6 support
Date: Thu, 13 Mar 2008 07:08:29 -0700 (PDT) [thread overview]
Message-ID: <956157.57545.qm@web30507.mail.mud.yahoo.com> (raw)
In-Reply-To: <1205414790-1710-1-git-send-email-bhalevy@panasas.com>
Did any body test nfs (v2 and v3) over ipv6 ?
do you guys claim "this feature suppose to work" ?
It did not work for me. Here are the details of
experiments I did (for me server and client is
same):
1) Kernel side : Linux-2.6.12-5 +
linux-2.6.12-rc6-CITI_NFS4_ALL-1.dif +
Chuck Lever Transport Patch
(http://oss.oracle.com/~cel/linux-2.6/2.6.12/release-notes.html)
2) User land (tools) side: libtirpc-0.1.7-1 +
rpcbind-0.1.4 + nfs-utils-1.1.1 + quota-3.12-5
(Ref:
http://nfsv4.bullopensource.org/patches/nfsv4_ipv6-2)
3) rpcbind suppose to recognize ipv6/ipv4 tcp/udp
protocols (after modifying /etc/netconfig). I did
softlink of /usr/bin/rpcbind to /sbin/portmap).
Then did "service portmap restart".
Then "service nfs restart". NFS services failed.
syslog messages:
Mar 13 19:32:20 DXi5500-12345 nfs: Starting NFS
services: succeeded
Mar 13 19:32:20 DXi5500-12345 nfs: rpc.rquotad startup
succeeded
Mar 13 19:32:20 DXi5500-12345 kernel: RPC: transport
(2/17) not supported
Mar 13 19:32:20 DXi5500-12345 last message repeated 2
times
Mar 13 19:32:20 DXi5500-12345 nfsd[12453]: nfssvc:
Input/output error
Mar 13 19:32:20 DXi5500-12345 nfs: rpc.nfsd startup
failed
Mar 13 19:32:20 DXi5500-12345 nfs: rpc.mountd startup
succeeded
Mar 13 19:32:20 DXi5500-12345 rpc.idmapd: nfsdreopen:
Opening '/proc/net/rpc/nfs4.idtoname/channel' failed:
errno 2 (No such file or directory)
Mar 13 19:32:20 DXi5500-12345 rpc.idmapd: nfsdreopen:
Opening '/proc/net/rpc/nfs4.nametoid/channel' failed:
errno 2 (No such file or directory)
Mar 13 19:32:20 DXi5500-12345 rpcidmapd: rpc.idmapd
-SIGHUP succeeded
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
next prev parent reply other threads:[~2008-03-13 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 13:26 [PATCH] nfs: fix encode_fsinfo_maxsz Benny Halevy
2008-03-13 14:08 ` Rajesham Gajjela [this message]
2008-03-13 16:21 ` Trond Myklebust
[not found] ` <1205425264.11399.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-03-13 16:27 ` Benny Halevy
2008-03-13 16:29 ` Fredric Isaman
2008-03-13 16:55 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2008-03-13 14:31 nfs over ipv6 support Rajesham Gajjela
[not found] ` <573299.38219.qm-NzHz0fVKiIyvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-03-13 18:13 ` Chuck Lever
2008-03-14 1:00 ` Rajesham Gajjela
[not found] ` <206342.91146.qm-uHTUF03blOmvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2008-03-14 14:45 ` Chuck Lever
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=956157.57545.qm@web30507.mail.mud.yahoo.com \
--to=rajeshamg@yahoo.com \
--cc=aime.le-rouzic@bull.net \
--cc=aurelien.charbon-Z51IpKcfGtLk1uMJSBkQmQ@public.gmane.org \
--cc=gilles.quillard@bull.net \
--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