From: Le Rouzic <aime.le-rouzic@bull.net>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Varun Chandramohan <varunc@linux.vnet.ibm.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Frank S Filz <ffilz@us.ibm.com>
Subject: Re: NFSD IPv6 support for 2.6.29
Date: Tue, 09 Dec 2008 13:37:20 +0100 [thread overview]
Message-ID: <493E6680.2050904@bull.net> (raw)
In-Reply-To: <AF604C91-2F1B-48A3-8E1D-84D5CBBB2856@oracle.com>
Chuck Lever a =E9crit :
>>>>>>> Bruce asked me to collect server-side IPv6 patches for upstream=
=2E
>>>>>>> I've collected the patches that have been posted on the list, a=
nd
>>>>>>> added some fixes of my own.
>>>>>>>
>>>>>>> Can you have a look at
>>>>>>>
>>>>>>> http://git.linux-nfs.org/?p=3Dcel/cel-2.6.git;a=3Dsummary
>>>>>>>
>>>>>>> tag cel-ipv6-10292008
>>>>>>>
>>>>>>> These have been build tested, but I haven't done any run-time
>>>>>>> testing yet.
>>>>>>>
>>>>>>> --=20
>>>>>>> Chuck Lever
>>>>>>> chuck[dot]lever[at]oracle[dot]com
>>>>>>
>> Hi
>> I have tested the "tag cel-ipv6-10292008" and some robustness tests
>> started simultaneously (connectathon, fsx, iozone, fss_stress, ffsb)=
=20
>> have
>> been running fine during several hours in IPV6 and IPV4.
>> I used the my nfs-utils package based on nfs-utils.1.1.2
>> (http://nfsv4.bullopensource.org/)
>
Hi,
I get an issue with AIX used as client in front of the above=20
snapshot used on a linux server.
=20
Doing the following on the AIX side:
=20
mount -o vers=3D4 nfs4gb:/ /mnt/nosec
cd /mnt/nosec
mkdir rep
cd rep
the command "ls" will fail with the follwing error on the AIX si=
de:
"kern:err|error unix: Client encounters unexpected=20
NFS4ERR_BAD_COOKIE error from server"
The problem happens with IPV6 and IPV4
=20
Best Regards
--=20
-----------------------------------------------------------------
Company : Bull, Architect of an Open World TM (www.bull.com)
Name : Aime Le Rouzic=20
Mail : Bull - BP 208 - 38432 Echirolles Cedex - France
E-Mail : aime.le-rouzic@bull.net
Phone : 33 (4) 76.29.75.51
=46ax : 33 (4) 76.29.75.18
-----------------------------------------------------------------=20
next prev parent reply other threads:[~2008-12-09 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 17:04 NFSD IPv6 support for 2.6.29 Chuck Lever
2008-10-30 3:09 ` Varun Chandramohan
2008-11-10 5:15 ` Varun Chandramohan
2008-11-12 5:57 ` Chuck Lever
2008-11-12 16:02 ` Le Rouzic
2008-11-12 16:20 ` Chuck Lever
2008-11-17 17:52 ` Le Rouzic
2008-11-17 18:19 ` Chuck Lever
2008-12-09 12:37 ` Le Rouzic [this message]
2008-12-09 16:24 ` Chuck Lever
2008-12-09 21:04 ` J. Bruce Fields
2008-12-10 14:48 ` Le Rouzic
2008-12-10 15:04 ` Trond Myklebust
[not found] ` <1228921485.2914.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-12-10 16:37 ` J. Bruce Fields
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=493E6680.2050904@bull.net \
--to=aime.le-rouzic@bull.net \
--cc=chuck.lever@oracle.com \
--cc=ffilz@us.ibm.com \
--cc=linux-nfs@vger.kernel.org \
--cc=varunc@linux.vnet.ibm.com \
/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.