From owner-freebsd-current@FreeBSD.ORG Tue May 26 12:50:10 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 AEF95106564A; Tue, 26 May 2009 12:50:10 +0000 (UTC) (envelope-from flo@kasimir.com) Received: from mail.solomo.de (mail.solomo.de [85.214.49.72]) by mx1.freebsd.org (Postfix) with ESMTP id 6378A8FC13; Tue, 26 May 2009 12:50:09 +0000 (UTC) (envelope-from flo@kasimir.com) Received: from localhost (localhost [127.0.0.1]) by mail.solomo.de (Postfix) with ESMTP id EA3753F4A7; Tue, 26 May 2009 14:36:29 +0200 (CEST) X-Virus-Scanned: amavisd-new at vistream.de Received: from mail.solomo.de ([127.0.0.1]) by localhost (mail.solomo.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Giu20uAwuHA7; Tue, 26 May 2009 14:36:17 +0200 (CEST) Received: from nibbler.vistream.local (relay3.vistream.de [87.139.10.28]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.solomo.de (Postfix) with ESMTPSA id D640C3F49E; Tue, 26 May 2009 14:36:17 +0200 (CEST) Message-ID: <4A1BE241.5030706@kasimir.com> Date: Tue, 26 May 2009 14:36:17 +0200 From: Florian Smeets User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090526 Shredder/3.0b3pre MIME-Version: 1.0 To: Larry Rosenman References: <3c1674c90905242253n544c3f0cqb10952f349391ce7@mail.gmail.com> <454b8cc37c60ab7af2663ba70ddbfd59.squirrel@webmail.lerctr.org> <5a9a181a12e9e4ef864d23ae063f7277.squirrel@webmail.lerctr.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Kip Macy Subject: Re: ZFS Crash 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, 26 May 2009 12:50:10 -0000 On 26.05.09 14:04, Larry Rosenman wrote: > On Mon, 25 May 2009, Larry Rosenman wrote: > >> On Mon, 25 May 2009, Larry Rosenman wrote: >> >>> after looking at the code, never mind the "don't call doadump", so we'll >>> get the textdump. >>> >>> Thanks rwatson for the textdump stuff! >>> >> Here is current stats before we crash. Does any of this look totally >> out of line? >> > It crashed again, but did *NOT* make it into ddb enough to do the textdump. > > It was hung with the backtrace (looks like the same, but I couldn't > scroll the screen back). > > Ideas? > > I'm really concerned that there is a problem. > Hi i guess I'm having a similar/the same problem. The panic looks the same, and the trace is a little different, I've had a lot of these panics on this machine, and the stack trace looked different quite often. The panic and show uma and show malloc can be found here: http://webmail.solomo.de/~flo/panic.txt I have a coredump written to swap, but this panic is very easy to trigger and it panics every time savecore runs... It is also easy to trigger this with a buildworld -j5. This is a quadcore Xeon with a a slow SATA disk and only 1GB of mem. (It's only a test machine, so i can test any suggestion.) This box used to run stable with kmem max set to 768M. Anything i can do? Cheers, Florian