Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Apr 2007 23:28:10 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        Doug Poland <doug@polands.org>
Cc:        freebsd-current@freebsd.org, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: new ZFS sysctls not working?
Message-ID:  <20070410032810.GA40459@xor.obsecurity.org>
In-Reply-To: <20070410030712.GB94010@polands.org>
References:  <20070409232654.GA93109@polands.org> <20070410010532.GA38535@xor.obsecurity.org> <20070410025020.GA94010@polands.org> <20070410025855.GA39926@xor.obsecurity.org> <20070410030712.GB94010@polands.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 09, 2007 at 10:07:12PM -0500, Doug Poland wrote:
> On Mon, Apr 09, 2007 at 10:58:55PM -0400, Kris Kennaway wrote:
> > On Mon, Apr 09, 2007 at 09:50:20PM -0500, Doug Poland wrote:
> > > On Mon, Apr 09, 2007 at 09:05:32PM -0400, Kris Kennaway wrote:
> > > > On Mon, Apr 09, 2007 at 06:26:54PM -0500, Doug Poland wrote:
> > > > > Hello,
> > > > >=20
> > > > > It would appear that the new sysctls for ZFS
> > > > > (vfs.zfs.arc_max/min) are not "taking".  i.e.,
> > > > >=20
> > > > > # cat /boot/loader.conf
> > > > > vfs.zfs.arc_max=3D134217728
> > > > > vfs.zfs.arc_min=3D134217728
> > > > >=20
> > > > > # sysctl -a | grep vfs.zfs.arc
> > > > > vfs.zfs.arc_max: 67108864
> > > > > vfs.zfs.arc_min: 67108864
> > > > >=20
> > > > > This is after a fresh cvsup run today around 10:00 CDT.
> > > >=20
> > > > Please provide more details of your system, e.g. sysctl
> > > > vm.kmem_size.
> > > >=20
> > > FreeBSD 7.0-CURRENT #0: Mon Apr  9 12:55:54 CDT 2007
> > >     djp@seth.polands.org:/usr/obj/usr/src/sys/GENERIC
> > > WARNING: WITNESS option enabled, expect reduced performance.
> > > Timecounter "i8254" frequency 1193182 Hz quality 0
> > > CPU: AMD Athlon(tm) processor (1403.19-MHz 686-class CPU)
> > >   Origin =3D "AuthenticAMD"  Id =3D 0x644  Stepping =3D 4
> > >   Features=3D0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PG=
E,MCA,CMOV,PAT,PSE36,MMX,FXSR>
> > >   AMD Features=3D0xc0440800<SYSCALL,<b18>,MMX+,3DNow!+,3DNow!>
> > > real memory  =3D 259981312 (247 MB)
> > > avail memory =3D 240451584 (229 MB)
> > >=20
> > > # sysctl -a | grep vm.kmem_size
> > > vm.kmem_size: 80662528
> > > vm.kmem_size_max: 335544320
> > > vm.kmem_size_scale: 3
> >=20
> > Yeah, you don't even have 128 MB of kmem available (only 76 MB), so
> > it's no surprise zfs refused to use that much ;-)
> >=20
> I was attempting to "portsnap extract" to a two disk ZFS mirror.  It
> would appear my ability to test ZFS is severly limited on this
> particular hardware configuration.  Sorry for the noise...

Well you can increase your kmem a bit, but yeah, it's probably not
going to perform very well because you're taking it away from userland
so there will be increased swap activity too.

Kris

--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)

iD8DBQFGGwRKWry0BWjoQKURAotRAKD0PXd8va5qt/OJHDTfeZ7sNSU1/wCg4qft
Mwo/1jFncUT3MC1ygAYPElc=
=B4ot
-----END PGP SIGNATURE-----

--3MwIy2ne0vdjdPXF--



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