From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boaz Harrosh Subject: Re: [pnfs] [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT case to use of do_last() Date: Thu, 25 Mar 2010 11:13:27 +0200 Message-ID: <4BAB2937.6050703@panasas.com> References: <4BAA3493.1030802@panasas.com> <20100324160037.GP30031@ZenIV.linux.org.uk> <4BAA3828.2070506@panasas.com> <20100324160754.GQ30031@ZenIV.linux.org.uk> <4BAA398C.5050901@panasas.com> <20100324163948.GR30031@ZenIV.linux.org.uk> <4BAA48A3.1030801@panasas.com> <4BAA4CAC.6060104@panasas.com> <4BAA5035.1060906@panasas.com> <1269453756.5982.33.camel@localhost.localdomain> <1269454208.5982.34.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Al Viro , linux-fsdevel , "J. Bruce Fields" , pNFS Mailing List , linux-kernel To: Trond Myklebust Return-path: In-Reply-To: <1269454208.5982.34.camel@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 03/24/2010 08:10 PM, Trond Myklebust wrote: > On Wed, 2010-03-24 at 14:02 -0400, Trond Myklebust wrote: >> I'd say you have a corruption issue either on the server side or on your >> client. > It is surely a corruption on the client. I've tested with an old server and it fails just the same. > By the way. Does this issue happen with NFSv4 too, or is it only > NFSv4.1? > > Trond > -o minorversion=0 or =1 does not matter. nfsv3 does not have that problem. (Same client different server though) Boaz