Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 May 2009 10:47:37 -0500 (CDT)
From:      Larry Rosenman <ler@lerctr.org>
To:        Florian Smeets <flo@kasimir.com>
Cc:        freebsd-current@freebsd.org, Kip Macy <kmacy@freebsd.org>
Subject:   Re: ZFS Crash
Message-ID:  <alpine.BSF.2.00.0905261046180.42298@borg>
In-Reply-To: <4A1BE241.5030706@kasimir.com>
References:  <alpine.BSF.2.00.0905250040230.1781@borg> <3c1674c90905242253n544c3f0cqb10952f349391ce7@mail.gmail.com> <454b8cc37c60ab7af2663ba70ddbfd59.squirrel@webmail.lerctr.org> <5a9a181a12e9e4ef864d23ae063f7277.squirrel@webmail.lerctr.org> <alpine.BSF.2.00.0905250803350.79867@borg> <alpine.BSF.2.00.0905260702300.1820@borg> <4A1BE241.5030706@kasimir.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 May 2009, Florian Smeets wrote:

> 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?
>
I've started running the below script every minute from cron.

If anyone wants to look at the data let me know (it's on a Resi DSL line, so
I don't want to run an http server).

I'm willing to give SSH accounts to @FreeBSD.org devs to look around.

script:

#!/bin/sh
DATE=`date +%Y%m%d.%H%M%S`
(echo "Uptime:";uptime;echo "vmstat -m:";vmstat -m
  echo "vmstat -z:";vmstat -z) >/home/ler/stats/${DATE}.stats
-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 512-248-2683                 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0905261046180.42298>