From owner-freebsd-current@FreeBSD.ORG Mon Jul 21 00:01:47 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 328D23A4; Mon, 21 Jul 2014 00:01:47 +0000 (UTC) Received: from borg.macktronics.com (borg.macktronics.com [209.181.253.68]) by mx1.freebsd.org (Postfix) with ESMTP id 0A22C2BCF; Mon, 21 Jul 2014 00:01:46 +0000 (UTC) Received: from olive.macktronics.com (olive.macktronics.com [209.181.253.67]) by borg.macktronics.com (Postfix) with ESMTP id 1D0D613C; Sun, 20 Jul 2014 18:53:18 -0500 (CDT) Date: Sun, 20 Jul 2014 18:53:18 -0500 (CDT) From: Dan Mack To: Steven Hartland Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 In-Reply-To: <4A0B8A1798484B3DB4DCD924A2DFEF22@multiplay.co.uk> Message-ID: References: <20140720140350.GA8498@borg.lerctr.org> <8D84B82C674B495DBF4951E0EE0D7117@multiplay.co.uk> <21dbecad27074fe34610bc587e6d0764@thebighonker.lerctr.org> <05c8bccf4faf5005881fbd2b22f35428@thebighonker.lerctr.org> <4A0B8A1798484B3DB4DCD924A2DFEF22@multiplay.co.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Larry Rosenman X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 21 Jul 2014 00:01:47 -0000 On Mon, 21 Jul 2014, Steven Hartland wrote: > ----- Original Message ----- From: "Larry Rosenman" > To: "Steven Hartland" > Cc: ; > Sent: Monday, July 21, 2014 12:22 AM > Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 > > >> On 2014-07-20 18:21, Steven Hartland wrote: >>> Can you try reverting r265321 and see if you still see the >>> same crash? >>> >>> Regards >>> Steve >> I'll do the revert, but it's been a ONE TIME hit. >> >> There was a followup to mine with a reproducible poudriere crash like mine. > > If you don't have a reproducable senario I'd hold off. > > Florian, is yours reproducable and can you send me > a pretty print of the crashing zio? > > Regards > Steve I think I may have hit the same problem; I'm going to stay connected to the console and see if it happens again; this is what I see currently with the back-trace: db> bt Tracing pid 0 tid 100070 td 0xfffff8000e088920 kdb_enter() at kdb_enter+0x3e/frame 0xfffffe085ef1d980 vpanic() at vpanic+0x146/frame 0xfffffe085ef1d9c0 panic() at panic+0x43/frame 0xfffffe085ef1da20 deadlkres() at deadlkres+0x35c/frame 0xfffffe085ef1da70 fork_exit() at fork_exit+0x84/frame 0xfffffe085ef1dab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe085ef1dab0 --- trap 0, rip = 0, rsp = 0xfffffe085ef1db70, rbp = 0 --- I just updated to I think 268921 earlier today and this is the first time I've had a panic (HEAD-268921 that is) I'll try to get some more data if I can get it back up and running. dan -- Dan Mack