Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 07 Aug 2009 16:00:05 -0400
From:      Boris Kochergin <spawk@acm.poly.edu>
To:        Pawel Jakub Dawidek <pjd@FreeBSD.org>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: ZFS RAID-Z panic on vdev failure + subsequent panics and hangs
Message-ID:  <4A7C87C5.1070608@acm.poly.edu>
In-Reply-To: <20090807193842.GA2487@garage.freebsd.pl>
References:  <4A78AA71.9050107@acm.poly.edu> <4A78AFB2.10103@acm.poly.edu> <20090805115621.GG1784@garage.freebsd.pl> <4A798A12.4070408@acm.poly.edu> <20090807073738.GA1607@garage.freebsd.pl> <20090807074400.GB1607@garage.freebsd.pl> <4A7C3002.8000003@acm.poly.edu> <20090807191334.GA1814@garage.freebsd.pl> <4A7C81CA.2040303@acm.poly.edu> <20090807193842.GA2487@garage.freebsd.pl>

next in thread | previous in thread | raw e-mail | index | archive | help
Pawel Jakub Dawidek wrote:
> On Fri, Aug 07, 2009 at 03:34:34PM -0400, Boris Kochergin wrote:
>   
>> Pawel Jakub Dawidek wrote:
>>     
>>> Yeah, that's strange indeed. Could you try:
>>>
>>> 	print ab->b_arc_node.list_prev
>>> 	print ab->b_arc_node.list_next
>>>
>>>  
>>>       
>> (kgdb) print ab->b_arc_node.list_prev
>> $1 = (struct list_node *) 0x1
>>     
>
> Yeah, list_prev is corrupted. If it panics on you everytime, I could
> send you a patch which will try to catch where the corruption occurs.
>
>   
I eventually get the arc_evict panic every time I successfully manage to 
mount the filesystem, but it usually panics (with the other backtrace) 
as soon as I try to mount it, or mount just hangs. I'll gladly try the 
patch, though--the data on the array is important to me. Thanks.

-Boris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A7C87C5.1070608>