From: steve <steve@steve-ss.com>
To: linux-nfs@vger.kernel.org
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: Re: NFSv4 client restriction
Date: Thu, 23 Feb 2012 16:42:46 +0100 [thread overview]
Message-ID: <4F465E76.4000201@steve-ss.com> (raw)
In-Reply-To: <4F464A4A.10403@fifthhorseman.net>
On 02/23/2012 03:16 PM, Daniel Kahn Gillmor wrote:
> On 02/23/2012 02:09 AM, steve wrote:
>> It is not recommended to use the pseudoroot fsid=0 stuff for Linux.
>>
>> See the nfs wiki: 'The linux implementation allows you to designate a
>> real filesystem as the pseudofilesystem, identifying that export with
>> the fsid=0 option; we no longer recommend this. Instead, on any recent
>> linux distribution, just list exports in /etc/exports exactly as you
>> would for NFSv2 or NFSv3.'
> I believe the last time this came up, i asked for a rationale or
> explanation. The only reason given [0] was from J. Bruce Fields:
I've never got to the bottom of this one either. I only know that it works.
>>> The main problem with the fsid=0 trick is that your v3 and v4 clients
>>> end up with different paths.
But if say, you're exporting /home and have /home bind mounted to your
pseudoroot, then the paths are exactly the same. You still mount -t nfsx
server:/home /client/somewhere for x=3 or x=4. No?
> So, if you have no v3 clients, i don't think there is any reason to
> avoid fsid=0 if it makes things cleaner for you. And removing fsid=0
> will require you to change /etc/fstab (or your automounter config) in
> all of your clients.
Please accept my apologies for butting in on this. I'm simply trying to
get some facts together.
Cheers,
Steve
next prev parent reply other threads:[~2012-02-23 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 19:24 NFSv4 client restriction Peter Horvath
2012-02-23 1:01 ` J. Bruce Fields
2012-02-23 1:24 ` Peter Horvath
2012-02-23 1:45 ` J. Bruce Fields
2012-02-23 7:09 ` steve
2012-02-23 10:25 ` Peter Horvath
2012-02-23 14:16 ` Daniel Kahn Gillmor
2012-02-23 15:42 ` steve [this message]
2012-02-29 22:32 ` J. Bruce Fields
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=4F465E76.4000201@steve-ss.com \
--to=steve@steve-ss.com \
--cc=dkg@fifthhorseman.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.