linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Ashish Sangwan <ashishsangwan2@gmail.com>
Cc: neilb@suse.com, linux-nfs@vger.kernel.org
Subject: Re: Handling of duplicate inode numbers for the directories in the nfs v3 kernel client
Date: Thu, 10 Jan 2019 15:33:20 -0500	[thread overview]
Message-ID: <20190110203320.GE15492@fieldses.org> (raw)
In-Reply-To: <CAOiN93=bh8WrCD8gZ+En4EfzTv2iHMn5n4w5=rYJOr6RbUkCKQ@mail.gmail.com>

On Thu, Dec 13, 2018 at 09:17:31AM +0530, Ashish Sangwan wrote:
> Thanks for the clarification!
> 
> On Thu, 13 Dec 2018, 4:15 am NeilBrown <neilb@suse.com wrote:
> >
> > On Thu, Dec 13 2018, Ashish Sangwan wrote:
> >
> > > Hi,
> > >
> > > Our NFS filer can sometimes return same inode number for different directories.
> >
> > Why?
> The NFS fileserver is handling file systems over different nodes at
> the same time.
> To the client however, we want to present with a single pseudo fsid
> (sent as part of the getattr) so that submounts can be avoided.

Out of curiosity, why do you want to avoid submounts?

--b.

  parent reply	other threads:[~2019-01-10 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 18:57 Handling of duplicate inode numbers for the directories in the nfs v3 kernel client Ashish Sangwan
2018-12-12 22:45 ` NeilBrown
2018-12-13  3:47   ` Ashish Sangwan
2018-12-13  3:55     ` NeilBrown
2019-01-10 20:33     ` J. Bruce Fields [this message]
2019-01-26  8:39       ` Ashish Sangwan
2018-12-13 16:26 ` Frank Filz
2018-12-14  5:11   ` Ashish Sangwan
2018-12-17 11:06     ` Jeff Layton

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=20190110203320.GE15492@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=ashishsangwan2@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.com \
    /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).