From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932074Ab0CXRPa (ORCPT ); Wed, 24 Mar 2010 13:15:30 -0400 Received: from daytona.panasas.com ([67.152.220.89]:17461 "EHLO daytona.int.panasas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754293Ab0CXRPW (ORCPT ); Wed, 24 Mar 2010 13:15:22 -0400 Message-ID: <4BAA48A3.1030801@panasas.com> Date: Wed, 24 Mar 2010 19:15:15 +0200 From: Boaz Harrosh User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3 MIME-Version: 1.0 To: Al Viro CC: linux-fsdevel , pNFS Mailing List , Benny Halevy , "J. Bruce Fields" , linux-kernel Subject: Re: [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT case to use of do_last() 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> In-Reply-To: <20100324163948.GR30031@ZenIV.linux.org.uk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Mar 2010 17:15:19.0041 (UTC) FILETIME=[9422EF10:01CACB75] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/24/2010 06:39 PM, Al Viro wrote: > On Wed, Mar 24, 2010 at 06:10:52PM +0200, Boaz Harrosh wrote: >> On 03/24/2010 06:07 PM, Al Viro wrote: >>> On Wed, Mar 24, 2010 at 06:04:56PM +0200, Boaz Harrosh wrote: >>>>> Bloody impressive... Does that happen to underlying fs or to what you >>>>> are seeing via NFS? >>>> >>>> Only via NFS. All local access is fine. >>>> >>>> After the corruption above I can cd to the local mount cp a fresh copy >>>> of .git/index file and play around just fine. >>>> Once I return to the NFS mounted directory, a git status will do it. >>>> It does not matter if caches are cold (Takes a long time) or hot it happens >>>> every time. >>>> >>>> Weird I know, I'm playing some more with it as we speak >>> >>> What happens if you export to box running older kernel *or* from box >>> running older kernel? IOW, is that nfsd or nfs client getting unhappy? >>> I'd suspect the latter, but... >> >> >> Good question, I'm just getting to that because currently it's all >> over localhost (same kernel, BTW inside a UML) >> >> I will try what you said. Please through any other tests on me, if needed. > As you suspected old-server+new-client fails. any-thing+old-client is fine. (two separate machines this time) > Very interesting... Just to see which path we are hitting: add > if (IS_ERR(nd->intent.open.file)) > printk("foo: %s", pathname); > right after > error = do_lookup(nd, &nd->last, path); > if (error) > goto exit; > in fs/namei.c:do_last() and see whether we are hitting it or not on objects > that get corrupted. Sorry was busy shifting setups, didn't see your mail, will do that next ... Thanks Boaz