public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: steve <steve@steve-ss.com>, whats_up@gmx.net, linux-nfs@vger.kernel.org
Subject: Re: mount hangs in NFS4+Kerberos setup
Date: Fri, 10 Feb 2012 13:51:41 -0500	[thread overview]
Message-ID: <20120210185141.GB5781@fieldses.org> (raw)
In-Reply-To: <4F35603A.5050508@fifthhorseman.net>

On Fri, Feb 10, 2012 at 01:21:46PM -0500, Daniel Kahn Gillmor wrote:
> On 02/10/2012 01:07 PM, steve wrote:
> > Officially, you should not export from a pseudo root. Please see the
> > last few lines in the link I sent.
> 
> That link offers the same assertion but no explanation for it.  Can you
> explain why that's the recommendation?
> 
> If an admin were to remove fsid=0 from their exports line, they'd also
> need to adjust the paths in all the connecting clients, right?

Yep.

The main problem with the fsid=0 trick is that your v3 and v4 clients
end up with different paths.

--b.

  reply	other threads:[~2012-02-10 18:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 14:45 mount hangs in NFS4+Kerberos setup whats_up
2012-02-10 14:52 ` Sven Geggus
2012-02-10 15:36 ` Andy Adamson
     [not found]   ` <20120210172554.5e89e364@little-poseidon>
2012-02-10 18:19     ` Andy Adamson
2012-02-13  9:32       ` whats_up
2012-02-10 17:17 ` steve
2012-02-10 17:41   ` whats_up
2012-02-10 18:07     ` steve
2012-02-10 18:21       ` Daniel Kahn Gillmor
2012-02-10 18:51         ` J. Bruce Fields [this message]
2012-02-10 19:06         ` steve
2012-02-10 19:13           ` J. Bruce Fields
2012-02-13 10:01       ` whats_up
2012-02-13 10:51     ` Sven Geggus
2012-02-13 18:50       ` whats_up
2012-02-13 18:55         ` Daniel Kahn Gillmor
2012-02-15  9:57         ` Sven Geggus

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=20120210185141.GB5781@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=dkg@fifthhorseman.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steve@steve-ss.com \
    --cc=whats_up@gmx.net \
    /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