Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 May 2012 22:26:53 +0100
From:      Anton Shterenlikht <mexas@bristol.ac.uk>
To:        Sergey Kandaurov <pluknet@gmail.com>, freebsd-current@freebsd.org
Subject:   Re: r235163: root: /etc/rc.d/sysctl: WARNING: sysctl vfs.nfs.access_cache_timeout does not exist.
Message-ID:  <20120510212653.GA23637@mech-cluster241.men.bris.ac.uk>
In-Reply-To: <20120510205121.GB23350@mech-cluster241.men.bris.ac.uk>
References:  <20120510103008.GA21311@mech-cluster241.men.bris.ac.uk> <CAE-mSOJJxK%2BHucY7QXo1qi2s-7EzEbii6PBM829E7qfyt7mC6A@mail.gmail.com> <20120510205121.GB23350@mech-cluster241.men.bris.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 10, 2012 at 09:51:22PM +0100, Anton Shterenlikht wrote:
> On Thu, May 10, 2012 at 06:11:28PM +0400, Sergey Kandaurov wrote:
> > On 10 May 2012 14:30, Anton Shterenlikht <mexas@bristol.ac.uk> wrote:
> > >
> > > On ia64 r235163:
> > >
> > > root: /etc/rc.d/sysctl: WARNING: sysctl vfs.nfs.access_cache_timeout does not exist.
> > >
> > > What is this about?
> > > After updating to this revision,
> > > I run mergemaster, as usual,
> > > with the setting to auto update
> > > all /etc files which I didn't touch.
> > 
> > I'd check your kernel config for 'options NFSCLIENT', so there is
> > sysctl vfs.oldnfs.access_cache_timeout instead, and you try to set
> > non-existing vfs.nfs.access_cache_timeout from /etc/sysctl.conf.
> > If it is so then all your sysctl vfs.nfs.xxx are named as vfs.oldnfs.xxx,
> > because the NFS implementation enabled with 'options NFSCLIENT'
> > considered old, and the NFS impl. enabled with 'options NFSCL' is the default.
> > My inner voice tells me that you have upgraded from quite old CURRENT
> > from the point when 'options NFSCLIENT' (old nfs) was default to the point
> > when 'options NFSCL' (new nfs implementation) became the default,
> > and you still have 'options NFSCLIENT' in your kernel config.
> > See /usr/src/UPDATING entry dated 20110427.
> 
> You are exactly right.
> 
> I don't even use NFS anyway.
> So I'll just remove it completely
> from my kernel.

oh no..
Seems I do need NFS kernel options for zfs.
If I remove NFS, I get:

Loading /boot/defaults/loader.conf 
/boot/kernel/kernel text=0x966fb0 data=0x96164+0x2161ac syms=[0x8+0x80718+0x8+0x76ed5]
/boot/kernel/zfs.ko text=0x22e4f8 data=0x9060+0x16de8 syms=[0x8+0x16c20+0x8+0x11725]
loading required module 'opensolaris'
/boot/kernel/opensolaris.ko text=0x3338 data=0x510+0x2030 syms=[0x8+0xcd8+0x8+0x872]
loading required module 'krpc'

KLD zfs.ko: depends on krpc - not available or version mismatch
kldload: can't load zfs: No such file or directory
/etc/rc: WARNING: Unable to load kernel module zfs

I guess now that zfs needs module acl_nfs4,
the latter needs NFS, right?

Or can module krpc be loaded instead?

Anyway, I put new NFS options in the kernel,
and now zfs works ok.

Thanks

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120510212653.GA23637>