From: Trond Myklebust Subject: Re: nfs exporting my stacked fs Date: 31 May 2003 01:44:27 +0200 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: References: <20030530233003.GA15469@ccpu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from pat.uio.no ([129.240.130.16]:49580 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S264072AbTE3XbO (ORCPT ); Fri, 30 May 2003 19:31:14 -0400 To: Andrew Sharp In-Reply-To: <20030530233003.GA15469@ccpu.com> List-Id: linux-fsdevel.vger.kernel.org >>>>> " " == Andrew Sharp writes: > Yes. At first I was annoyed that the Linux NFS client peeks at > the file handle, because sometimes I want to change it for the > same file, but then it turns out that the solution to another > problem of mine fixes that as well. And now it sounds like the > v4 file handle won't be considered opaque for the client any > more. All v2/v3/v4 file handles are opaque as far as the client is concerned. The only issue is that of uniqueness. Whereas NFSv2/v3 do not support the concept of a filehandle that is not unique over time, NFSv4 does (in theory) by means of the concept of "volatile filehandles". Note though that NFSv4 volatile filehandles have a number of unsolved race conditions associated to them. I would recommend that people stay away from them if at all possible. > I take it then that the fsid returned by ->statfs is largely > not used right now? My version of nfs-utils (1.0) doesn't > support the fsid option in config files, so I've just hacked > the kernel to get me through this part of the development > phase. The fsid is unused for NFSv2/v3. It is very important for NFSv4, as the latter allows the server to cross mount points (rather like the somewhat ill-defined "nohide" option did for NFSv2/v3). In NFSv4, the client is expected to automount the new partition if we cross a mount point on the server. Crossing a mount point is detected by means of the fsid change... > I'm guessing that all or part of this stuff is handled a bit > differently in 2.5? Not yet. However it will be once we fix the NFSv4 behaviour. Cheers, Trond