From owner-freebsd-fs@FreeBSD.ORG Fri Sep 17 08:39:53 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D45AA1065670 for ; Fri, 17 Sep 2010 08:39:53 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id AF0FA8FC18 for ; Fri, 17 Sep 2010 08:39:53 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta03.emeryville.ca.mail.comcast.net with comcast id 7kfs1f0051smiN4A3kfs6r; Fri, 17 Sep 2010 08:39:52 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta20.emeryville.ca.mail.comcast.net with comcast id 7kfr1f0043LrwQ28gkfrBc; Fri, 17 Sep 2010 08:39:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 5B97D9B427; Fri, 17 Sep 2010 01:39:51 -0700 (PDT) Date: Fri, 17 Sep 2010 01:39:51 -0700 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20100917083951.GA48183@icarus.home.lan> References: <20100917061216.GA44936@icarus.home.lan> <4C9325BE.7000101@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C9325BE.7000101@icyb.net.ua> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: gil@vidals.net, freebsd-fs@freebsd.org Subject: Re: vm.kmem_size for stability to avoid kernel panics? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2010 08:39:53 -0000 On Fri, Sep 17, 2010 at 11:24:30AM +0300, Andriy Gapon wrote: > on 17/09/2010 09:12 Jeremy Chadwick said the following: > > # Disable UMA (uma(9)) for ZFS; amd64 was moved to exclusively use UMA > > # on 2010/05/24. > > # http://lists.freebsd.org/pipermail/freebsd-stable/2010-June/057162.html > > vfs.zfs.zio.use_uma="0" > > I think that that commit was reverted and zero is a default value now. Yeah, it was. However, because it's impossible to determine in every single case what the kernel build date is on a readers' machine (ex. people who search Google, find the mailing list post, etc.), I mention it as a safety net. I should have mentioned this one as well (I don't include it in our loader.conf because our RELENG_8 systems all have kernels built after the below commit) -- the recent change of vfs.zfs.vdev.max_pending's value, from 35 to 10: vfs.zfs.vdev.max_pending="10" And that's based on this commit: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c#rev1.4.2.1 I say this while on a soapbox, but I'm trying to do so politely. This is why I continue to harp/rant/whine about the need for better communication about all the changes that happen, especially in ZFS, to the RELENG_x (non-HEAD) branches. That means literally every commit. Most users/admins do not follow commits or mailing lists, instead resorting to Google to find solutions, etc... I also know that committers/engineers can't dedicate that amount of time either. I just wish we could find a compromise that works well. A lot of places use blogs for this task. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |