Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ming Lei <Ming.Lei@riverbed.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: Re: nfs4.1  pseudo filesystem
Date: Fri, 11 Oct 2013 16:58:36 -0400	[thread overview]
Message-ID: <20131011205836.GC22160@fieldses.org> (raw)
In-Reply-To: <20131011182942.GA22160@fieldses.org>

On Fri, Oct 11, 2013 at 02:29:42PM -0400, J. Bruce Fields wrote:
> On Fri, Oct 11, 2013 at 04:51:29PM +0000, Ming Lei wrote:
> > I want to cherry-pick a few subdirectories under say /root, but I don't want to specifies all these mount directories one by one just like NFSv2/3.
> 
> Well, you're kind of stuck enumerating them whether as exports or bind
> mounts.
> 
> > Does pseudo filesystem in kernel v3.11 work well enough?
> 
> But it should work anyway, yes.
> 
> Oh, wait, I see the problem: it doesn't work well if you're exporting
> subdirectories and not full filesystems.  Unless you do something
> special at the export points  (e.g. mount --bind them over themselves),
> knfsd doesn't know when you've crossed an export point.

I wonder if exportfs should be taught to mark export points as
junctions.  That might fix this kind of problem?

It might mean creating junctions never get cleaned up, which is ugly
though perhaps unlikely to be a serious problem in practice.

--b.

  reply	other threads:[~2013-10-11 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 21:39 nfs4.1 pseudo filesystem Ming Lei
2013-10-11 16:30 ` J. Bruce Fields
2013-10-11 16:51   ` Ming Lei
2013-10-11 18:29     ` J. Bruce Fields
2013-10-11 20:58       ` J. Bruce Fields [this message]
2013-10-11 21:04         ` Chuck Lever
2013-10-12  6:40 ` Wangminlan

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=20131011205836.GC22160@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Ming.Lei@riverbed.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.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