From owner-freebsd-fs@FreeBSD.ORG Mon Mar 15 08:32:13 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 1DE81106567B; Mon, 15 Mar 2010 08:32:13 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop2.sarenet.es (proxypop2.sarenet.es [194.30.0.95]) by mx1.freebsd.org (Postfix) with ESMTP id C53318FC26; Mon, 15 Mar 2010 08:32:12 +0000 (UTC) Received: from [172.16.1.204] (unknown [192.148.167.2]) by proxypop2.sarenet.es (Postfix) with ESMTP id 2867073646; Mon, 15 Mar 2010 09:32:11 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20100313152429.GH3209@garage.freebsd.pl> Date: Mon, 15 Mar 2010 09:32:10 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <864468D4-DCE9-493B-9280-00E5FAB2A05C@lassitu.de> <20100309122954.GE3155@garage.freebsd.pl> <20100309125815.GF3155@garage.freebsd.pl> <20100310110202.GA1715@garage.freebsd.pl> <20100310173143.GD1715@garage.freebsd.pl> <27A6DF40-2EA8-4CFC-9E42-DD995E2F9342@sarenet.es> <20100313152429.GH3209@garage.freebsd.pl> To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.1077) Cc: freebsd-fs@freebsd.org Subject: Re: Many processes stuck in zfs 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: Mon, 15 Mar 2010 08:32:13 -0000 On Mar 13, 2010, at 4:24 PM, Pawel Jakub Dawidek wrote: > On Fri, Mar 12, 2010 at 11:12:49AM +0100, Borja Marcos wrote: >>=20 >> On Mar 10, 2010, at 6:31 PM, Pawel Jakub Dawidek wrote: >>=20 >>> Hmm, interesting. Especially those two traces: >>>=20 >>> Tracing command zfs pid 1820 tid 100105 td 0xffffff0002ca4000 >>=20 >> Just in case something was wrong, I wiped the two virtual machines = and started everything again. The two virtual systems were acting a bit = weird, giving lots of LORs. I don't know why, maybe something was = corrupted, these virtual machines have been panicked and restarted many = times. >>=20 >> So, experiment repeated again, fresh start. Still deadlocking pretty = soon if I start, say, 5 or 6 tar processes. Traces follow. >=20 > Are you able to dump the kernel memory and make it available for me > somewhere? I'd need to look at it wit GDB, as DDB is not enough here, > I'm afraid. Sure. Do you have access to VMWare Fusion? I can create a snapshot of = the deadlocked system and make it available to you. Borja.