From owner-freebsd-stable@FreeBSD.ORG Thu May 25 17:58:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4303216B1B1 for ; Thu, 25 May 2006 17:58:07 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C8CE43D5F for ; Thu, 25 May 2006 17:58:05 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 27799 invoked from network); 25 May 2006 17:58:03 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[217.50.131.179]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 25 May 2006 17:58:03 -0000 Date: Thu, 25 May 2006 19:57:56 +0200 From: Fabian Keil To: "Arno J. Klaassen" Message-ID: <20060525195756.7eaf4aa2@localhost> In-Reply-To: References: X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_YVbxbPVeI+oV.pyGxTmd_z/"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org Subject: Re: kmem leak in tmpmfs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 17:58:18 -0000 --Sig_YVbxbPVeI+oV.pyGxTmd_z/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Arno J. Klaassen" wrote: > Hello, >=20 > I get a very easy to reproduce panic on 6.1-STABLE : >=20 > /etc/periodic/weekly/310.locate panics with >=20 > panic: kmem_malloc(4096): kmem_map too small: 335544320 total > allocated > This box has nothing particular, apart from maybe a large number > of stamp-file based test-databases (with a lot of zero-sized > files named .key=3Dvalue). > Producing this bug is easy : >=20 > - set tmpmfs=3D"YES" and set tmpsize greater than around 220m > - start /etc/periodic/weekly/310.locate (and nothing else!) > - wait two-three hours and bang >=20 > Last test is with tmpfs=3D1024m and I monitored df -h /tmp and > vmstat -zm every minute; when the system panics, last output is : >=20 > Filesystem Size Used Avail Capacity Mounted on > /dev/md0 989M 219M 691M 24% /var/tmp >=20 > vmstat -zm | fgrep md0 > md0: 512, 0, 453257, 15, 453437 >=20 > I'm quite not an expert, but looks to me as if md0 use stays > almost 100% in kmem and is never swapped (as it is supposed to do > by default according to the man-page). The rc script has different defaults than mdmfs: fk@TP51 ~ $grep tmpmfs_flags /etc/defaults/rc.conf=20 tmpmfs_flags=3D"-S -M" # Extra mdmfs options for the mfs /tmp You probably want to ditch the "-M". Fabian --=20 http://www.fabiankeil.de/ --Sig_YVbxbPVeI+oV.pyGxTmd_z/ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdfApjV8GA4rMKUQRAlQgAJ93eF5uhuyA9wjYsv11DVvxalTLJACeJZvg 7u40GgI18Heskl0UMJMUSBI= =wt/E -----END PGP SIGNATURE----- --Sig_YVbxbPVeI+oV.pyGxTmd_z/--