Date: Fri, 5 Oct 2007 02:00:46 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: freebsd-fs@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: ZFS kmem_map too small. Message-ID: <20071005000046.GC92272@garage.freebsd.pl>
next in thread | raw e-mail | index | archive | help
--bKyqfOwhbdpXa4YI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi.
We'are about to branch RELENG_7 and I'd like to start discussion with
folks that experience 'kmem_map too small' panic with the latest HEAD.
I'm trying hard to reproduce it and I can't, so I need to gather more
info how you are able to provoke this panic.
What I did was to rsync 200 FreeBSD src trees from one directory to
another on the same ZFS file system. It worked fine.
The system I'm using is i386 and the only tuning I did is bigger
kmem_map. From my /boot/loader.conf:
vm.kmem_size=3D629145600
vm.kmem_size_max=3D629145600
The machine is dual core Pentium D 3GHz with 1GB of RAM. My pool is:
lcf:root:/tank/0# zpool status
pool: tank
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
ad4 ONLINE 0 0 0
ad5 ONLINE 0 0 0
ad6 ONLINE 0 0 0
ad7 ONLINE 0 0 0
errors: No known data errors
If you can still see those panic, please let me know as soon as possible
and try to describe what your workload looks like, how to reproduce it,
etc. I'd really like ZFS to be rock-stable for 7.0 even on i386.
--=20
Pawel Jakub Dawidek http://www.wheel.pl
pjd@FreeBSD.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
--bKyqfOwhbdpXa4YI
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFHBX6uForvXbEpPzQRAnb3AJ9Qa9S4pmIeA1RRbfq/f8krB/jTQACgsjBL
PJp2ZwshSM4CPetRugv6Id8=
=ONnA
-----END PGP SIGNATURE-----
--bKyqfOwhbdpXa4YI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071005000046.GC92272>