Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756586AbXLJOTt (ORCPT ); Mon, 10 Dec 2007 09:19:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753737AbXLJOTl (ORCPT ); Mon, 10 Dec 2007 09:19:41 -0500 Received: from ug-out-1314.google.com ([66.249.92.172]:53456 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751917AbXLJOTk (ORCPT ); Mon, 10 Dec 2007 09:19:40 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=xNPGibqK3H5kBJL6CXq7rrfaVjfhdOBHKHJfy9gggm3JCmUUp4BrYfcQJLRgYJr7W3SeAVeSjN4H8RZrvSXmoPpYCBHhbMhYHP7prp3fk+NumP6Qfezl93oLGIi7ZSSWsmCujG4RqNrguT8KYk6Th4+XiArNhky2TqN/2LjEL3E= From: Maxim Levitsky To: Neil Brown Subject: Re: 2.6.24-rc3-git4 NFS crossmnt regression Date: Mon, 10 Dec 2007 16:19:12 +0200 User-Agent: KMail/1.9.6 Cc: "Rafael J. Wysocki" , Andrew Morton , Trond Myklebust , gnome42@gmail.com, linux-kernel@vger.kernel.org, bfields@fieldses.org, "Eric W. Biederman" , "Denis V. Lunev" , linux-nfs@vger.kernel.org References: <200712090220.44543.maximlevitsky@gmail.com> <18268.51342.353887.178014@notabene.brown> In-Reply-To: <18268.51342.353887.178014@notabene.brown> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712101619.12522.maximlevitsky@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1955 Lines: 62 ... > It is best not to use nohide - we should probably mark it as > 'legacy'. > > Simply export the top level mountpoint as 'crossmnt' and everything > below there will be exported. > > > Where should I put those options in root file-system export or in submount export? > > crossmnt goes at the top. nohide goes in the submount. Both have > the same general effect though with subtle differences. > You don't need both (though that doesn't hurt). > Just use crossmnt at the top, Then you don't need to mention the > lower level filesystems at all. > > > ... > > (I decided to switch to NFS4 only due to the lack of ability to see underlying mounts) > > > > All of this should work fine with v3. Once you have the right patch > for the crossmnt bug applied, if you have further problems post them > to linux-nfs@vger.kernel.org. > > NeilBrown > Big thanks, Still NFS server just don't want to accept the connection I noticed that if I first mount with -tnfs, unmount, and then mount with -tnfs4, it works Assuming that [PATCH 2.6.24-rc4] proc: Remove/Fix proc generic d_revalidate is the fix for crossmnt bug, I applied it to both client and server, but no luck. Still see empty folders. my /etc/exports file (on old box): / *(insecure,rw,fsid=0,crossmnt,async,anonuid=1000,anongid=100) /dev *(insecure,rw,fsid=1,async,anonuid=1000,anongid=100) /mnt/disk2 *(insecure,rw,async,anonuid=1000,anongid=100) It is totally insecure, but I have just home network, and it is behind firewall, and besides I am testing this now. I am afraid that I am doing something wrong since I don't know nfs well yet, and especially nfs4 (But I want to make nfs4 work too) Best regards, Maxim Levitsky -- 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/