From: "J. Bruce Fields" Subject: Re: NFSD IPv6 support for 2.6.29 Date: Wed, 10 Dec 2008 11:37:15 -0500 Message-ID: <20081210163715.GC28263@fieldses.org> References: <491AFE09.2010803@bull.net> <2BF8FCDB-0C6D-430E-B2AE-4C293E30A1AE@oracle.com> <4921AF45.4070009@bull.net> <493E6680.2050904@bull.net> <9F0B9CDF-DDA7-4752-B08D-EC43A3D664E1@oracle.com> <20081209210407.GE8596@fieldses.org> <493FD6C0.7070906@bull.net> <1228921485.2914.14.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Le Rouzic , Chuck Lever , Varun Chandramohan , Linux NFS Mailing List , Frank S Filz To: Trond Myklebust Return-path: Received: from mail.fieldses.org ([66.93.2.214]:34567 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757275AbYLJQh2 (ORCPT ); Wed, 10 Dec 2008 11:37:28 -0500 In-Reply-To: <1228921485.2914.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Wed, Dec 10, 2008 at 10:04:45AM -0500, Trond Myklebust wrote: > On Wed, 2008-12-10 at 15:48 +0100, Le Rouzic wrote: > > > 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 . > > While there may be a server bug here, it definitely is wrong for the AIX > client to be sending a READDIR request with a cookie argument of '1'. > RFC3530 is adamant that > > For READDIR arguments, cookie values of 1 and 2 should not be > used and for READDIR results cookie values of 0, 1, and 2 should > not be returned. > > That said, I'd love to understand why the server replied to the first > READDIR request with no entries, and yet with EOF not set. Is it perhaps > because the 'dircount' was too small, Bruce? Oops, my bad--mention of readdir should have reminded me of commit b726e923ea4d216027e466aa602d914e4b4a63af "Fix nfsd truncation of readdir results", which fixed a problem like that; that went into -rc4, so worth retesting with -rc4. Also, spurious NFS4ERR_SAME calls are a symptom of the ctime resolution problem so worth retrying with a different filesystem with you're using ext2/3. --b.