From: mehta kiran <kiranmehta1981@yahoo.com>
Subject: Re: exportfs nohide option for nfsv4
Date: Thu, 10 Mar 2005 07:43:33 -0800 (PST)
Message-ID: <20050310154334.34824.qmail@web51607.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: nfs@lists.sourceforge.net
To: "J. Bruce Fields" <bfields@fieldses.org>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

Hi , 

    This is the part of man page i am referring to .

1. Normally,  if  a  server
2. exports  two filesystems one of which is mounted 3.
on the other, then the client will have to mount  
4. both filesystems  explicitly  to get access to
5. them.  If it just mounts the parent, it  will  see 
6. an  empty directory  at  the place where the other
7. filesystem is mounted.  That filesystem is 
8. hidden".
9. Setting the nohide option on a filesystem causes
10.it not  to  be hidden.

from lines 5-10 i understand that if client mounts
only parent directory , child directory is hidden
to client.To make this accessbile to client , exportfs
should use nohide option , but in
my example i have explicitly exported child 
directory.

thanks,
 --kiran


--- "J. Bruce Fields" <bfields@fieldses.org> wrote:
> On Thu, Mar 10, 2005 at 07:14:50AM -0800, mehta
> kiran wrote:
> > what i feel is that when i have explicitly
> exported 
> > exported /export/exp1 and /export i should not
> require
> > to specify no hide option(I have explicitly
> exported
> > /export/exp1 and so why should i ask nfs to
> > unhide it)
> 
> In v4, the client expects *all* of the exports to be
> stitched together
> into a single namespace.
> 
> In v3, mounting is done with a separate protocol. 
> So, for example, it's
> possible that you can get a different file by
> mounting "/a" and then
> looking up "b" than you would get if you mounted
> "/a/b".
> 
> To v3 clients, exporting /export/exp1 makes it
> possible for clients to
> mount /export/exp1, without allowing them to mount
> /export and then
> traverse to /export/exp1.
> 
> From the point of view of someone that only uses v4,
> yes, the "nohide"
> looks redundant since the only way to get to that
> export is by
> traversing from the parent.  But for v3 it isn't
> redundant, so this
> requirement is not likely to go away.
> 
> (I suppose as a special case we could treat "fsid=0"
> as implying the
> crossmnt option for v4 clients.  I don't know
> whether that's a good
> idea.)
> 
> >    I am referring to  man page of exports.
> 
> Which part of "man exports" are you referring to? 
> Could you quote the
> relevant passage?  I don't see anything that says
> "nohide" is
> unnecessary in this case.
> 
> --b.
> 
> 
>
-------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users.
> Discover which products truly live up to the hype.
> Start reading now.
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs