Re: [nfsv4] Questions about NFS deamons

Rick Macklem <rmacklem@uoguelph.ca> Tue, 15 July 2008 14:42 UTC

Return-Path: <nfsv4-bounces@ietf.org>
X-Original-To: nfsv4-archive@megatron.ietf.org
Delivered-To: ietfarch-nfsv4-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC4693A686A; Tue, 15 Jul 2008 07:42:02 -0700 (PDT)
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D08D3A686A for <nfsv4@core3.amsl.com>; Tue, 15 Jul 2008 07:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GN5xZZN1QVCx for <nfsv4@core3.amsl.com>; Tue, 15 Jul 2008 07:41:56 -0700 (PDT)
Received: from phoenix.cs.uoguelph.ca (phoenix.cs.uoguelph.ca [131.104.94.216]) by core3.amsl.com (Postfix) with ESMTP id EA1323A677C for <nfsv4@ietf.org>; Tue, 15 Jul 2008 07:41:55 -0700 (PDT)
Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by phoenix.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id m6FEgLJx022641; Tue, 15 Jul 2008 10:42:22 -0400
Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id m6FEqkM04466; Tue, 15 Jul 2008 10:52:47 -0400 (EDT)
X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs
Date: Tue, 15 Jul 2008 10:52:46 -0400
From: Rick Macklem <rmacklem@uoguelph.ca>
X-X-Sender: rmacklem@muncher.cs.uoguelph.ca
To: msalcedo@inf.puc-rio.br
In-Reply-To: <61892.189.122.3.26.1216094886.squirrel@webmail.inf.puc-rio.br>
Message-ID: <Pine.GSO.4.63.0807151043050.2870@muncher.cs.uoguelph.ca>
References: <61892.189.122.3.26.1216094886.squirrel@webmail.inf.puc-rio.br>
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.63 on 131.104.94.216
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] Questions about NFS deamons
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: nfsv4-bounces@ietf.org
Errors-To: nfsv4-bounces@ietf.org


On Tue, 15 Jul 2008, msalcedo@inf.puc-rio.br wrote:

> Hello all,
>
> I really want to understand how NFS deamons works. Please, I need your help.
>
This is implementation specific, but I'll try and give generic answers
that, hopefully, won't be too inaccurate for most nfs servers.

> What's the function of the deamon mountd (or rpc.mountd)? How it works?
>
Typically, it talks a separate protocol (the mount protocol) for NFSv2 and
NFSv3 clients (this protocol is no longer used for NFSv4). On some
implementations it also handles the exporting file systems, by maintaining
a database of what is exported and informing the kernel of these exports
via a system call.

> Meet all requests of NFS clients for mounting filesystems ?
See above. For NFSv2 and v3, a client normally talks to mountd first, via 
the mount protocol, in order to acquire an exported file handle for the
mount point. After that, the client uses the nfs protocol.

> Mountd don't "speak" with clients directly  but through the nfsd (another
> deamon)? So, nfsd get clients requests and pass to mountd? Mountd only
> meets nfsd requests ?
Nope, see above.

>
> How nfsd and mountd interacts?
>
There is very little. The nfsd uses the exported file system information 
and that might have been set up by the mountd daemon.

For NFSv4, there is no mount protocol, so a mountd daemon may not be 
needed at all. (If it is needed for an implementation, it will probably
be related to setting up the exported file system information.)

rick
_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4