From: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
To: Sreeram B S <public-sreeramb-HgOvQuBEEgTQT0dZR+AlfA@plane.gmane.org>
Cc: public-linux-nfs-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org
Subject: Re: NFS mounts and its propagation
Date: Wed, 28 Sep 2011 16:02:49 -0700 [thread overview]
Message-ID: <4E83A799.1090303@linux.vnet.ibm.com> (raw)
In-Reply-To: <4E805C16.4030509@netapp.com>
On 09/26/2011 04:03 AM, Sreeram B S wrote:
> Hi,
> I am Sreeram. This question is related to NFS.
> I have a typical scenario. Please assume that there are 3 machines M1,
> M2, M3. Each of them are having directories /tmp/abc in them. All the
> NFS permissions are set appropriately.
> Now, a user mounts M2's /tmp/abc on M1's /tmp/abc by issuing mount
> command on M1. Mount is successful.
> Then the user mounts M3's /tmp/abc on M2's /tmp/abc by issuing mount
> command on M2. Mount successful.
> Now I would expect the contents of M3's /tmp/abc to be shown as output
> of 'ls' issue on M1. But this is not happening. I am unable to
> comprehend the reason. Could you please guide me?
What are you seeing instead? Are you seeing M2's contents on M1?
Did you try to change the order of the experiment? i.e First mount M3 on
M2 and then mount M2 on M1? Just curious to see if there is any change
in the behavior.
Thanks,
JV
>
> According to me, the contents of M3 should have shown up in M1's 'ls'
> command, because the /tmp/abc of M1 is nothing but a *live* reflection
> of /tmp/abc of M2. So whatever changes are done to M2's /tmp/abc should
> be reflected on M1. Here, M2's /tmp/abc is mounting M3's /tmp/abc and so
> this change should be reflected on M1's /tmp/abc as well. But this isn't
> happening.
>
> Kindly suggest if I am incorrect in my understanding or usage.
> The command I am using is:
>
> On M1: mount -t nfs M2:/tmp/abc /tmp/abc
> On M2: mount -t nfs M3:/tmp/abc /tmp/abc
>
> Regards,
> Sreeram
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-09-28 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 11:03 NFS mounts and its propagation Sreeram B S
2011-09-28 23:02 ` Venkateswararao Jujjuri [this message]
2011-09-29 0:08 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2011-09-26 12:22 Benny Halevy
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=4E83A799.1090303@linux.vnet.ibm.com \
--to=jvrao@linux.vnet.ibm.com \
--cc=public-linux-nfs-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org \
--cc=public-sreeramb-HgOvQuBEEgTQT0dZR+AlfA@plane.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).