From: Neil Brown <neilb@cse.unsw.edu.au>
To: "Kendrick M. Smith" <kmsmith@umich.edu>
Cc: nfs@lists.sourceforge.net, <linux-fsdevel@vger.kernel.org>,
nfsv4-wg@citi.umich.edu
Subject: Re: NFSv4 pseudo filesystem
Date: Sat, 11 May 2002 16:31:11 +1000 (EST) [thread overview]
Message-ID: <abieaj$6rf$2@main.gmane.org> (raw)
In-Reply-To: message from Kendrick M. Smith on Friday May 10
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
next prev parent reply other threads:[~2002-05-11 6:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <message from Anton Altaparmakov on Saturday May 11>
[not found] ` <message from Kendrick M. Smith on Friday May 10>
[not found] ` <Pine.SOL.4.44.0205101340370.27306-100000@mspacman.gpcc.itd.umich.edu>
2002-05-10 18:18 ` NFSv4 pseudo filesystem Christoph Hellwig
2002-05-10 23:14 ` H. Peter Anvin
2002-05-11 6:31 ` Neil Brown [this message]
[not found] ` <15580.47791.999102.980645@notabene.cse.unsw.edu.au>
2002-05-11 17:39 ` David Chow
2002-05-11 20:19 ` NFS export operations question and BUG report Anton Altaparmakov
2002-05-11 20:21 ` Anton Altaparmakov
2002-05-11 21:08 ` Anton Altaparmakov
2002-05-11 21:43 ` Neil Brown
2002-05-11 23:09 ` Anton Altaparmakov
2002-05-11 21:18 ` Neil Brown
2002-05-11 22:38 ` Anton Altaparmakov
2002-05-12 7:39 ` Alexander Viro
[not found] ` <Pine.GSO.4.21.0205120330410.23398-100000@weyl.math.psu.edu >
2002-05-12 12:00 ` Anton Altaparmakov
2002-05-12 16:20 ` Jan Harkes
2002-05-13 6:54 ` Neil Brown
2002-05-11 0:13 NFSv4 pseudo filesystem Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 18:12 Kendrick M. Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='abieaj$6rf$2@main.gmane.org' \
--to=neilb@cse.unsw.edu.au \
--cc=kmsmith@umich.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4-wg@citi.umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox