Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756756AbXLGSOs (ORCPT ); Fri, 7 Dec 2007 13:14:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753999AbXLGSOl (ORCPT ); Fri, 7 Dec 2007 13:14:41 -0500 Received: from wa-out-1112.google.com ([209.85.146.178]:43776 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754078AbXLGSOk (ORCPT ); Fri, 7 Dec 2007 13:14:40 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rKIC3OpIzw7GPZQnI4rI3z0XG7XwnfOjOeAcestzmaCE2nrAuFL7+WCNQDZHeoK01kR2hh7UB31SXxM/Cei4s1vMBFY3Dfah0fMEVlzKpQMTaDcRQDspWeCwg5ASEAwHJI8GJiKxK806AF/4vlT0I70vKVEcW1xvSrbxmu8+GvE= Message-ID: Date: Fri, 7 Dec 2007 13:14:34 -0500 From: Shane To: "Andrew Morton" Subject: Re: 2.6.24-rc3-git4 NFS crossmnt regression Cc: linux-kernel@vger.kernel.org, "Trond Myklebust" , "J. Bruce Fields" , "Rafael J. Wysocki" In-Reply-To: <20071207040219.e231cbc7.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071207040219.e231cbc7.akpm@linux-foundation.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1575 Lines: 47 On Dec 7, 2007 7:02 AM, Andrew Morton wrote: ... > > 2.6.24-rc3-git1 is last known good kernel. The problem also exists > > with the latest snap 2.6.24-rc4-git4. NFS server is 2.6.23-rc9 and > > is unchanged. > > hm, there have been no nfs changes since 2.6.24-rc4. Ok, but the problem seems to have appeared before 2.6.24-rc4. > > It is easily reproducible here, hopefully for the person who > > knows how to debug it too :) > > > > I guess a full set of the commands which you typed to reproduce this would > help. Server is 2.6.23-rc9 and is exporting: /dirA/dirB 10.10.20.0/255.255.255.0(rw,async,no_root_squash,no_subtree_check,insecure,crossmnt) /dirA/dirB/dirC 10.10.20.0/255.255.255.0(rw,async,no_root_squash,no_subtree_check,insecure) /dirA/dirB/dirD 10.10.20.0/255.255.255.0(rw,async,no_root_squash,no_subtree_check,insecure) The NFS client (Core2 SMP) 2.6.24-rc3-git4: NFS-server:/dirA/dirB /dirA/dirB nfs auto,rsize=16384,wsize=16384,hard,intr,users,exec,nfsvers=3,tcp,nolock,actimeo=0 Then on the client when the new kernel has booted: ls /dirA/dirB --> normal listing ls /dirA/dirB/dirC --> Stale NFS file handle ls /dirA/dirB/dirD --> Stale NFS file handle I will do a few more builds/boots and check -rc3-git2 and -rc3-git3. Will report back shortly, Shane -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/