From: Steve Dickson <SteveD@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Harald Dunkel <harri@afaics.de>, linux-nfs@vger.kernel.org
Subject: Re: NFSv4 fsid=0 export still necessary?
Date: Wed, 07 Dec 2011 16:17:35 -0500 [thread overview]
Message-ID: <4EDFD7EF.4060909@RedHat.com> (raw)
In-Reply-To: <20111207163252.GB20079@fieldses.org>
On 12/07/2011 11:32 AM, J. Bruce Fields wrote:
> On Wed, Dec 07, 2011 at 11:30:38AM -0500, Steve Dickson wrote:
>>
>>
>> On 12/05/2011 08:10 PM, J. Bruce Fields wrote:
>>> On Sat, Dec 03, 2011 at 11:51:19AM -0500, Steve Dickson wrote:
>>>> No, the fsid=0 export option is no longer necessary to make v4
>>>> exports compatible with v2/v3 exports. When the fsid option
>>>> is not set, the default root is define as "/" which allows
>>>> the v4 clients to mount the same exports as does the v2/v3 clients.
>>>>
>>>> Now if you do not what "/" as your default root, you can
>>>> set fsid to something like fsid=/export. This will
>>>> change to default root to the /export directory which
>>>> means your v4 clients will only be able to access exports
>>>> under the /export directory.
>>>
>>> I actually have some old patches that allow you to use an alternate root
>>> for all NFS versions; you'd do something like:
>>>
>>> /exports *(ro, root)
>>> /exports/foo *(rw)
>>> /exports/bar *(rw)
>>>
>>> and then a v2, v3, or v4 client would mount server:/foo or server:/bar.
>>>
>>> But that was just a fun project, it wasn't clear to me whether anyone
>>> wanted it particularly.
>>>
>>> Also, that didn't seem like a great user interface. I'd rather have
>>> something like
>>>
>>> rootpath=/exports
>>> foo *(rw)
>>> bar *(rw)
>>>
>>> Actually, as long as we were doing that I'd rather replace /etc/exports
>>> entirely; maybe do something like
>>>
>>> [nfsd]
>>> rootpath=/exports
>>> [export "foo"]
>>> clients=*
>>> options=rw
>>> [exports "bar"]
>>> clients=*
>>> options=rw
>>>
>>> And also use the same file for other nfsd parameters:
>>>
>>> [nfsd]
>>> versions=2,3,4,4.1
>>> threads=8
>>> rootpath=/exports
>>> [export "foo"]
>>> ...
>> I kinda like this idea... In the systemd world, its less
>> error prone to have daemons read their own configuration
>> files...
>>
>> Where would this new file live and what would be called?
>
> I'm not sure.... Where did you end up putting the file for nfs mount
> configuration?
In /etc... /etc/nfsmount.conf... but /etc/default seems to be popular
these days...
steved.
prev parent reply other threads:[~2011-12-07 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 11:21 NFSv4 fsid=0 export still necessary? Harald Dunkel
2011-12-03 13:56 ` Jim Rees
2011-12-03 16:51 ` Steve Dickson
2011-12-06 1:10 ` J. Bruce Fields
2011-12-07 16:30 ` Steve Dickson
2011-12-07 16:32 ` J. Bruce Fields
2011-12-07 21:17 ` Steve Dickson [this message]
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=4EDFD7EF.4060909@RedHat.com \
--to=steved@redhat.com \
--cc=bfields@fieldses.org \
--cc=harri@afaics.de \
--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;
as well as URLs for NNTP newsgroup(s).