From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Le Rouzic <aime.le-rouzic@bull.net>,
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, 9 Dec 2008 16:04:07 -0500 [thread overview]
Message-ID: <20081209210407.GE8596@fieldses.org> (raw)
In-Reply-To: <9F0B9CDF-DDA7-4752-B08D-EC43A3D664E1@oracle.com>
On Tue, Dec 09, 2008 at 11:24:46AM -0500, Chuck Lever wrote:
> On Dec 9, 2008, at Dec 9, 2008, 7:37 AM, Le Rouzic wrote:
>> Chuck Lever a =C3=A9crit :
>>
>>>>>>>>> Bruce asked me to collect server-side IPv6 patches for =20
>>>>>>>>> upstream.
>>>>>>>>> I've collected the patches that have been posted on the=20
>>>>>>>>> list, and
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Chuck Lever
>>>>>>>>> chuck[dot]lever[at]oracle[dot]com
>>>>>>>>
>>>> Hi
>>>> I have tested the "tag cel-ipv6-10292008" and some robustness test=
s
>>>> started simultaneously (connectathon, fsx, iozone, fss_stress, ffs=
b)
>>>> 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
>> snapshot used on a linux server.
>>
>> Doing the following on the AIX side:
>>
>> 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 =20
>> side:
>> "kern:err|error unix: Client encounters unexpected
>> NFS4ERR_BAD_COOKIE error from server"
>>
>> The problem happens with IPV6 and IPV4
>
> This is probably an issue with NFSv4 proper. Bruce?
Somebody needs to look at a network trace of the above commands, and
find the request that got the BAD_COOKIE return. It should be to a
readdir request. Check whether the cookie the client provides in that
request was in fact returned from a previous readdir--if so, this is
probably a server bug, if not, probably a client bug.
Also note there's known problems between an AIX client an linux NFSv4
server when the exported filesystem is ext2 or ext3; xfs, for example,
should work. (The problem is inadequate ctime resolution on ext2 and
ext3).
--b.
next prev parent reply other threads:[~2008-12-09 21:04 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
2008-12-09 16:24 ` Chuck Lever
2008-12-09 21:04 ` J. Bruce Fields [this message]
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=20081209210407.GE8596@fieldses.org \
--to=bfields@fieldses.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox