From: dE <de.techno@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: Re: How do you get /proc/fs/nfs/exports to populate?
Date: Tue, 29 Dec 2015 08:47:24 +0530 [thread overview]
Message-ID: <5681FB44.3020704@gmail.com> (raw)
In-Reply-To: <20151228102116.4f687c6e@tlielax.poochiereds.net>
Thanks for clearing that up. Explains the erratic behavior without mountd.
On 12/28/15 20:51, Jeff Layton wrote:
> On Mon, 28 Dec 2015 15:11:03 +0530
> dE <de.techno@gmail.com> wrote:
>
>> Ok, got it.
>>
>> It happens that those are made after a mount request.
>>
> Well, there is no such thing as a mount request, per-se in NFSv4. What
> happens is that you try to walk down to the point where you're mounting
> and access that inode, and nfsd upcalls to mountd to see whether that's
> allowed. That populates the cache.
>
> You can't really run nfsd without mountd (or something equivalent)
> since something needs to populate the exports table. If you're running
> a v4-only server though, then mountd doesn't need to be network-facing
> however.
>
>> On 12/26/15 17:29, dE wrote:
>>> Hi!
>>> I'm running nfs-utils without init script or systemd unit assistance.
>>>
>>> Since I'm using nfsv4, I'm eliminating the need to start mountd.
>>>
>>> Now if mountd is gone, who populates /proc/fs/nfs/exports?
>>>
>>> But even after running mountd (after an exportfs -a), this file still
>>> does not have any entries.
>>>
>>> Running rpc.nfsd with --
>>>
>>> rpc.nfsd -d --syslog --port 10000
>>>
>>> rpc.mountd runs without any arguments.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-12-29 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 11:59 How do you get /proc/fs/nfs/exports to populate? dE
2015-12-28 9:41 ` dE
2015-12-28 15:21 ` Jeff Layton
2015-12-29 3:17 ` dE [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=5681FB44.3020704@gmail.com \
--to=de.techno@gmail.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;
as well as URLs for NNTP newsgroup(s).