From owner-freebsd-current@FreeBSD.ORG Tue Feb 3 14:16:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE2BB1065674; Tue, 3 Feb 2009 14:16:03 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 7325F8FC16; Tue, 3 Feb 2009 14:16:03 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.21.169] (helo=beastie.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LUM3l-0006BA-NE; Tue, 03 Feb 2009 22:15:29 +0800 Message-ID: <4988519E.2070103@micom.mng.net> Date: Tue, 03 Feb 2009 22:15:58 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.19 (X11/20090127) MIME-Version: 1.0 To: Peter Schuller References: <6eb82e0902010024o4094b3a6q3186f2109029a67a@mail.gmail.com> <20090201105815.GA73985@hyperion.scode.org> In-Reply-To: <20090201105815.GA73985@hyperion.scode.org> X-Enigmail-Version: 0.95.7 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: pjd@freebsd.org, FreeBSD Current , Rong-en Fan Subject: Re: process hang in zfs->io_ ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2009 14:16:04 -0000 Peter Schuller wrote: >> I'm running current as of 20080130 on an amd64 box. I can make >> processes stuck in zfs->io_ (output truncated in ddb and top) when I >> make some packages via ports tinderbox. The ports tinderbox access >> local disk via nfs (I also tried nullfs). >> >> ddb output of ps and alltrace can be found at >> >> http://www.rafan.org/FreeBSD/zfs/textdump.zfs.20090130.txt >> >> Any ideas? >> > > A workaround is to disable the ZIL (vfs.zfs.zil_disable="1"), if you > can afford that on the system in question. It will break the > durability of fsync(), but retain it's write barrier semantics. > > Btw, does anyone have a good grasp of the status of this bug? I have > seen vague referenced to it being a memory related deadlock for > example, but that's about it. Is the cause known but difficult to fix, > or just unknown? > I've observed similar system hang when I tried to run svn update on FreeBSD head repo from 2 local directories simultaneously. I might be doing something wrong and as I remember I reproduced it a couple of times. It is i386 CURRENT (r187663M) machine and loader.conf settings are: vm.kmem_size="1024M" vm.kmem_size_max="1024M" vfs.zfs.arc_max="100M" thanks, Ganbold