public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: <wabenbau@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
Date: Mon, 2 Feb 2015 16:19:21 +0100	[thread overview]
Message-ID: <20150202161921.39f4c14c@hal9000.localdomain> (raw)
In-Reply-To: <20150202083750.565760a4@digimed.co.uk>

Am Montag, 02.02.2015 um 08:37
schrieb Neil Bothwick <neil@digimed.co.uk>:

> On Mon, 2 Feb 2015 02:01:11 +0100, wabenbau@gmail.com wrote:
> 
> > > It's got nothing to do with the init system used. That message
> > > tells you what to do to try to mount the NFS shares when you
> > > boot, but unless you have suitable mount options or kernel
> > > config, that attempt will fail.  
> > 
> > Maybe I don't exactly understand what you are trying to tell me
> > because of my lousy English. 
> > 
> > Of course you also need the right mount options and kernel config.
> > But since nfsmount doesn't exist anymore, the "rpc stuff" isn't
> > started by the OpenRC init system until you add nfsclient to the
> > right runlevel. 
> > 
> The problem is that the mount command fails g=however you run it, from
> either init system or from a shell. It fails with "invalid mount
> options" because it now defaults to NFS V4.2 even if it is not
> enabled in the kernel. You need to either enable 4.2 or specifically
> set nfsver=4 to work around this.

Thanks for the explanation. My NFS servers are running Ubuntu 14.04.1
LTS. Only my clients are gentoo systems. And on the clients I have no
NFS 4 support in the kernel and I also don't have to specify nfsver=4. 
Maybe this problem only occurs with recent NFS versions on the server.

Regards
wabe


  reply	other threads:[~2015-02-02 15:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 21:18 [gentoo-user] [NOTE] New default behavior in latest nfs-utils (1.3.2-r1) walt
2015-02-01 22:41 ` [gentoo-user] " walt
2015-02-01 23:32   ` wabenbau
2015-02-02  0:12     ` Neil Bothwick
2015-02-02  1:01       ` wabenbau
2015-02-02  8:37         ` Neil Bothwick
2015-02-02 15:19           ` wabenbau [this message]
2015-02-02 15:33             ` Stefan G. Weichinger
2015-02-02 15:55               ` Holger Hoffstätte
2015-02-02 17:47                 ` Rich Freeman
2015-02-02 18:02                 ` Stefan G. Weichinger
2015-02-02 21:35                   ` Neil Bothwick
2015-02-02 21:48                     ` Stefan G. Weichinger
2015-02-02 15:45             ` Rich Freeman
2015-02-02  0:31     ` walt
2015-02-02  1:07       ` wabenbau
2015-02-02  1:35       ` wabenbau
2015-02-02  2:15         ` Rich Freeman
2015-02-02 18:37           ` Tom H
2015-02-02 18:29       ` Tom H
2015-02-03  1:46         ` walt
2015-02-03 11:29           ` Tom H
2015-02-04  0:05             ` walt
2015-02-22 12:51               ` Tom H
2015-02-02 17:57 ` [gentoo-user] " Tom H

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=20150202161921.39f4c14c@hal9000.localdomain \
    --to=wabenbau@gmail.com \
    --cc=gentoo-user@lists.gentoo.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