From: steve <steve@steve-ss.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: whats_up@gmx.net, linux-nfs@vger.kernel.org
Subject: Re: mount hangs in NFS4+Kerberos setup
Date: Fri, 10 Feb 2012 20:06:31 +0100 [thread overview]
Message-ID: <4F356AB7.7070408@steve-ss.com> (raw)
In-Reply-To: <4F35603A.5050508@fifthhorseman.net>
On 02/10/2012 07:21 PM, 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?
Sorry, no. I can however explain why we changed: We were having problems
with idmapd uid:gid mappings from the bind mount and just as an
experiment we tried the old way. Problem solved.
>
> 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?
>
> --dkg
No. If you are exporting /export fsid-0 and crossmnt-ing /export/opt,
you mount server:/opt client/somewhere. The only file you change is
/etc/exports on the server, to contain the old style mount spec.
/opt yourIPs(rw,sec=none:sys:krb5. . .)
The client sees exactly he same path.
HTH
Steve
next prev parent reply other threads:[~2012-02-10 19:06 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
2012-02-10 19:06 ` steve [this message]
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=4F356AB7.7070408@steve-ss.com \
--to=steve@steve-ss.com \
--cc=dkg@fifthhorseman.net \
--cc=linux-nfs@vger.kernel.org \
--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