Re: Delays on "first" access to a NFS mount

["J. Bruce Fields" <bfields@fieldses.org>]

On Thu, Mar 08, 2007 at 10:51:04AM +1100, Neil Brown wrote:
> Well, if you export a different root filesystem to each diskless
> client, or if you export /home to some places and /backup to others,
> then you already have the potential for a different pseudo filesystem
> for each client.  My little hacky shell script above essentially
> merges them all which might be OK, or might not.

I think we want a single export tree, parts of which clients may or may
not have permission to see, rather than try to support per-client
namespaces.  If nothing else, secinfo becomes a bit weird otherwise (do
you tell the client that it can use auth_unix security for this
filesystem, if actually using auth_unix might result in the client
seeing a *different* filesystem?).

> I was just looking at the RFC again and saw this in section 7.3:
> 
>    Based on the construction of the server's name space, it is possible
>    that multiple pseudo filesystems may exist.  For example,
> 
>    /a         pseudo filesystem
>    /a/b       real filesystem
>    /a/b/c     pseudo filesystem
>    /a/b/c/d   real filesystem
> 
>    Each of the pseudo filesystems are considered separate entities and
>    therefore will have a unique fsid.

Hah.

> That adds a whole new dimension of complexity..... do we really want
> to go there?

We certainly aren't required to support every weird configuration that
the RFC allows.

--b.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs