From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: NFSv4 pseudo filesystem Date: Sat, 11 May 2002 16:31:11 +1000 (EST) Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: nfs@lists.sourceforge.net, , nfsv4-wg@citi.umich.edu Return-path: Received: From notabene ([129.94.242.45] == bartok.orchestra.cse.unsw.EDU.AU) (for ) (for ) (for ) (for ) By tone With Smtp ; Sat, 11 May 2002 16:31:32 +1000 To: "Kendrick M. Smith" In-Reply-To: message from Kendrick M. Smith on Friday May 10 List-Id: linux-fsdevel.vger.kernel.org On Friday May 10, kmsmith@umich.edu wrote: > > Proposal 3: Build up the pseudofs inside the 2.5 'nfsd' filesystem, > say in a directory nfsd/pseudofs which is created when the nfsd > filesystem is mounted. The exportfs utility would be responsible > for creating the necesary subdirectories, then hanging the exports > off the leaves with mount --bind, before starting nfsd. > > As I see it, the disadvantage of proposal 3 is that it is a little > tricky to construct persistent filehandles ("persistent" in the sense > that an old filehandle is still recognize after the server is rebooted). > One solution would be to use an MD5 or SHA hash of the pathname as the > filehandle. The hash could be computed in userspace and passed into > the kernel somehow. I would go for 3, and don't care about persistent file handles. Just use volatile filehandles for this bit of the namespace. NeilBrown