Re: NFSD IPv6 support for 2.6.29

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



J. Bruce Fields a écrit :

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 écrit :

Bruce asked me to collect server-side IPv6 patches for upstream. I've collected the patches that have been posted on the list, and
added some fixes of my own.

Can you have a look at

http://git.linux-nfs.org/?p=cel/cel-2.6.git;a=summary

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 tests
started simultaneously (connectathon, fsx, iozone, fss_stress, ffsb)
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=4 nfs4gb:/ /mnt/nosec
    cd /mnt/nosec
    mkdir rep
    cd rep

the command "ls" will fail with the follwing error on the AIX 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.
 Hi,
I joined at this mail two wireshark traces. One when it was working (trace_2.6.27-rc3)
 and the other one with the error(trace_2.6.28-rc2).
It looks to come because the operation NVERIFY which was returned NFS_OK before now returns NFS4ERR_SAME making AIX retrying the readdir with an incremented cookie .

 Cheers

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




--
-----------------------------------------------------------------
Company : Bull, Architect of an Open World TM (www.bull.com)
Name : Aime Le Rouzic Mail : Bull - BP 208 - 38432 Echirolles Cedex - France
E-Mail  : aime.le-rouzic@xxxxxxxx
Phone   : 33 (4) 76.29.75.51
Fax     : 33 (4) 76.29.75.18
-----------------------------------------------------------------

Attachment: trace_2.6.27-rc3
Description: Binary data

Attachment: trace_2.6.28-rc2
Description: Binary data


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux