Hi ,
I am using RHEL 4 GA.
i created directories /export , /export/exp1.
Then i started all the nfs daemons.
I mounted a disk on /export/exp1.
Then i exported /export using
exportfs -o rw,no_root_squash,fsid=0 *:/export
I exported /export/exp1 using
exportfs -o rw,no_root_squash *:/export/exp1
I mounted exported fs on client side using
mount -t nfs4 server:/ /share
but i am not able to see contents of /share/exp1
When i used nohide attribute for exporting fs
then everyting works fine.
As per man page , nohide is not needed if the
filesystems mounted on child directories are
exported.
Please let me know if i ma wrong
thanks,
--kiran
__________________________________
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
-------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
one change.
As per man page , nohide is not needed if the
filesystems mounted on child directories are not
exported.So that user can access them even if
top level direcotry is exported
--- mehta kiran <[email protected]> wrote:
> Hi ,
> I am using RHEL 4 GA.
> i created directories /export ,
> /export/exp1.
> Then i started all the nfs daemons.
> I mounted a disk on /export/exp1.
>
> Then i exported /export using
> exportfs -o rw,no_root_squash,fsid=0
> *:/export
>
> I exported /export/exp1 using
> exportfs -o rw,no_root_squash *:/export/exp1
>
> I mounted exported fs on client side using
> mount -t nfs4 server:/ /share
>
> but i am not able to see contents of
> /share/exp1
> When i used nohide attribute for exporting fs
> then everyting works fine.
>
> As per man page , nohide is not needed if the
> filesystems mounted on child directories are
> exported.
> Please let me know if i ma wrong
>
> thanks,
> --kiran
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Easier than ever with enhanced search.
> Learn more.
> http://info.mail.yahoo.com/mail_250
>
>
>
-------------------------------------------------------
> 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 - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
-------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Thu, Mar 10, 2005 at 04:07:22AM -0800, mehta kiran wrote:
> Hi ,
> I am using RHEL 4 GA.
> i created directories /export , /export/exp1.
> Then i started all the nfs daemons.
> I mounted a disk on /export/exp1.
>
> Then i exported /export using
> exportfs -o rw,no_root_squash,fsid=0 *:/export
>
> I exported /export/exp1 using
> exportfs -o rw,no_root_squash *:/export/exp1
>
> I mounted exported fs on client side using
> mount -t nfs4 server:/ /share
>
> but i am not able to see contents of /share/exp1
> When i used nohide attribute for exporting fs
> then everyting works fine.
>
> As per man page , nohide is not needed if the
> filesystems mounted on child directories are
> exported.
> Please let me know if i ma wrong
Could you point out which part of which manpage you're referring to?
The nohide option *is* (as you've seen) required in this case. (Well,
either that or "crossmnt" on the parent export.)
--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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
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)
I am referring to man page of exports.
Please let me know if i am wrong.
thanks,
-- kiran
--- "J. Bruce Fields" <[email protected]> wrote:
> On Thu, Mar 10, 2005 at 04:07:22AM -0800, mehta
> kiran wrote:
> > Hi ,
> > I am using RHEL 4 GA.
> > i created directories /export ,
> /export/exp1.
> > Then i started all the nfs daemons.
> > I mounted a disk on /export/exp1.
> >
> > Then i exported /export using
> > exportfs -o rw,no_root_squash,fsid=0
> *:/export
> >
> > I exported /export/exp1 using
> > exportfs -o rw,no_root_squash
> *:/export/exp1
> >
> > I mounted exported fs on client side using
> > mount -t nfs4 server:/ /share
> >
> > but i am not able to see contents of
> /share/exp1
> > When i used nohide attribute for exporting
> fs
> > then everyting works fine.
> >
> > As per man page , nohide is not needed if
> the
> > filesystems mounted on child directories are
> > exported.
> > Please let me know if i ma wrong
>
> Could you point out which part of which manpage
> you're referring to?
>
> The nohide option *is* (as you've seen) required in
> this case. (Well,
> either that or "crossmnt" on the parent export.)
>
> --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 - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
-------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
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" <[email protected]> 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 - [email protected]
> 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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Thu, Mar 10, 2005 at 07:43:33AM -0800, mehta kiran wrote:
> 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.
Note the first sentence: "if a server exports two filesystems
one of which is mounted on the other..."
So the man page is dealing with exactly you case--when you
have explicitly exported both the parent and the child. I'm
not sure how the man page could be made clearer.
--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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Sorry , i was bit confused.
Its clear to me now.
Though server has exported parent and all child
filesystems , client has mounted only parent.
As client has not explicitly mounted child filesystem,
child filesystem is not accessible to it(client)
and so to make it accessible nohide option should be
used so that child need not be mounted separately or
explicitly by client.
thanks for your replies,
--kiran
--- "J. Bruce Fields" <[email protected]> wrote:
> On Thu, Mar 10, 2005 at 07:43:33AM -0800, mehta
> kiran wrote:
> > 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.
>
> Note the first sentence: "if a server exports two
> filesystems
> one of which is mounted on the other..."
>
> So the man page is dealing with exactly you
> case--when you
> have explicitly exported both the parent and the
> child. I'm
> not sure how the man page could be made clearer.
>
> --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 - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
-------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs