Date: Mon, 30 Apr 2007 23:30:43 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Peter Schuller <peter.schuller@infidyne.com> Cc: freebsd-fs@FreeBSD.org, Craig Boston <craig@xfoil.gank.org>, freebsd-current@FreeBSD.org Subject: Re: ZFS committed to the FreeBSD base. Message-ID: <20070430213043.GF67738@garage.freebsd.pl> In-Reply-To: <46365F76.7090708@infidyne.com> References: <20070406025700.GB98545@garage.freebsd.pl> <20070407025644.GC8831@cicely12.cicely.de> <20070407131353.GE63916@garage.freebsd.pl> <4617A3A6.60804@kasimir.com> <20070407165759.GG8831@cicely12.cicely.de> <20070407180319.GH8831@cicely12.cicely.de> <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <46365F76.7090708@infidyne.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--cz6wLo+OExbGG7q/
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Apr 30, 2007 at 11:28:22PM +0200, Peter Schuller wrote:
> > Hi, just wanted to chime in that I'm experiencing the same panic with
> > a fresh -CURRENT.
>=20
> I am also/still seeing the "kmem_map too small" panic on a tree cvsup:ed
> around April 27.
>=20
> I can consistently trigger it by doing "rsync -a /usr/ports
> /somepool/somepath", with both /usr and /somepool being on ZFS
> (different pools). This is on a machine with 1 GB memory, with the kmem
> size being 320 MB as per default.
>=20
> The kstat.zfs.misc.arcstats.size never jumps; the "solaris" memory usage
> never significantly jumps - stays between about 80 MB and 150 MB at all
> times. It does not even consistently increase in size within this range
> - it goes up and down.
>=20
> In terms of absolute sizes, nothing in the output of vmstat -m, except
> solaris, is even approaching the sizes we are talking about (everything
> is a handful of megs at most).
>=20
> Watching "top" during the rsync I can see wired memory steadily
> increasing. Starting at about 110 megs or so after startup (including
> parts of my desktop), it begins consistently increasing when I run the
> rsync. in this case I started to approach 200 megs. When rsync was done
> (ran it with -v this time) reading the source directory and began
> copying files, the growth of wired memory increased significantly in
> speed (it was up to 280 MB or so in under 30 seconds).
>=20
> Killing rsync did not cause the wired total to go down.
>=20
> Any suggestions on whether there is something else to monitor to find
> out what is using all the memory?
>=20
> zfs_kmem_alloc() always allocates with M_SOLARIS.
> kmem_cache_{create,alloc} don't, but they seem to be allocating very
> small amounts of memory (could there be leakage of a huge number of
> these?). Is it expected that ZFS would allocate significant amount of
> memory that is not categorized as M_SOLARIS?
>=20
> Could there be fragmentation going on? Are there very large allocations,
> relative to the 320 MB kmem size, intermixed with small allocations?
>=20
> Anything I can do in terms of testing that would help debug this, beyond
> what has already been done and reported on on -current?
What you're seeing is probably another problem, which was described
already. Try tunning kern.maxvnodes down to 3/4 of the current value,
see if that helps and please report back.
--=20
Pawel Jakub Dawidek http://www.wheel.pl
pjd@FreeBSD.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
--cz6wLo+OExbGG7q/
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)
iD8DBQFGNmADForvXbEpPzQRAoSIAKC/vuP7XWzvba1h2MJOTI5iDTBZ6wCeLoDz
isJ4AqbPWD6IYslc6ByUQPo=
=Kopf
-----END PGP SIGNATURE-----
--cz6wLo+OExbGG7q/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070430213043.GF67738>