From owner-freebsd-current@FreeBSD.ORG Sun Feb 1 10:58:17 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 CB998106566C for ; Sun, 1 Feb 2009 10:58:17 +0000 (UTC) (envelope-from scode@hyperion.scode.org) Received: from hyperion.scode.org (cl-1361.ams-04.nl.sixxs.net [IPv6:2001:960:2:550::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8D4BD8FC13 for ; Sun, 1 Feb 2009 10:58:17 +0000 (UTC) (envelope-from scode@hyperion.scode.org) Received: by hyperion.scode.org (Postfix, from userid 1001) id C992C23C4C2; Sun, 1 Feb 2009 11:58:15 +0100 (CET) Date: Sun, 1 Feb 2009 11:58:15 +0100 From: Peter Schuller To: Rong-en Fan Message-ID: <20090201105815.GA73985@hyperion.scode.org> References: <6eb82e0902010024o4094b3a6q3186f2109029a67a@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <6eb82e0902010024o4094b3a6q3186f2109029a67a@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD Current 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: Sun, 01 Feb 2009 10:58:18 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > 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). >=20 > ddb output of ps and alltrace can be found at >=20 > http://www.rafan.org/FreeBSD/zfs/textdump.zfs.20090130.txt >=20 > Any ideas? A workaround is to disable the ZIL (vfs.zfs.zil_disable=3D"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? --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmFgEcACgkQDNor2+l1i32RUACeLZkYmr7Co6Lp6gdbIUZbHwWI OfQAn3+GnhDt2RbggpLvKpxtlsUDb0mu =alh+ -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--