All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "J.A. Magallón" <jamagallon@ono.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: Questions and problems with NFS4
Date: Fri, 30 Jul 2010 14:47:38 -0400	[thread overview]
Message-ID: <20100730184738.GF21729@fieldses.org> (raw)
In-Reply-To: <20100730021837.65549fa7@werewolf.home>

On Fri, Jul 30, 2010 at 02:18:37AM +0200, J.A. Magallón wrote:
> First of all, plz correct me if this is in some kind of wiki, web page or
> the like, but I have not been able to find it. All this things should be
> on a document somewhere, perhaps even in the kernel itself...

Agreed.

> These are the things I have found out (thanks to your answers...).
> I'm a long time unix admin, not new to NFS, but all this things were not
> obvious to me, so perhaps they deserve to be in a document, something like
> "NFS 3 to 4 migration for dummy admins":
> 
> - Everything just works if you mount shares as nfs4. Even, if you have a
>   bunch of linux boxen with recent kernel/nfs-utils, probably you are
>   already doing nfs4... modern mount tries nfs4 first.
> 
> - Using nfsroot with fsid=0 is not mandatory, nor bind-mounting everything
>   under some /export (like many documents say), that only forces you to

We should update that documentation.

>   use the old way of specifying paths in the server (absolute, not
>   relative to /export).
> 
> - Even if you use nfsroot(fsid=0), and you mount it on the client
>   at /somepoint, you are not forced to mount everything else under
>   /somepoint (plz, correct me if I'm wrong).
> 
> - You can strip your server for NFS4, but not too much... Old daemons
>   are still needed locally. For example, you can get rid of NFS2 and
>   UDP for nfsd (-N 2 -U, -any os still uses NFS2??-), and old
>   mount protocols (-N 1 -N 2 for mountd)...
> 
> - ... but they can be firewalled, use is just local
> 
> - portmap/rpcbind is not needed, but still used because nfsd is not
>   yet proper clean for only-nfs4-behavior.
> 
> There are also some things I have not been able to discover, like
> using the interesting things of NFS4:
> 
> - How do you activate delegations ? Is this an automatic thing, or
>   do I have to add any option somewhere ?

It's automatic.  You can turn them off on the server side with
/proc/sys/fs/leases-enable.  They'll be turned off automatically if the
server can't open a tcp connection back to the client (for example, if
the client is behind a NAT).

> - How do you use cache ? Many docs talk about fsc option, but man
>   does not mention it (nfs-utils 1.2.2).
>   I have tried to use cachefiles module, and cachefilesd, but
>   when I try to run it, I get:

I haven't used that.  I don't believe there's anything NFSv4-specific
about it.

--b.

      reply	other threads:[~2010-07-30 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 22:46 Questions and problems with NFS4 J.A. Magallón
2010-07-28  2:28 ` Bian Naimeng
2010-07-28 17:14   ` J. Bruce Fields
2010-07-28 18:08 ` Chuck Lever
2010-07-30  0:18   ` J.A. Magallón
2010-07-30 18:47     ` J. Bruce Fields [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=20100730184738.GF21729@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.