From owner-freebsd-fs@FreeBSD.ORG Tue Aug 11 20:06:39 2009 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 94C9D1065674 for ; Tue, 11 Aug 2009 20:06:39 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 5A6D98FC39 for ; Tue, 11 Aug 2009 20:06:39 +0000 (UTC) Received: (qmail 87540 invoked from network); 11 Aug 2009 20:06:38 -0000 Received: from unknown (HELO ?192.168.0.137?) (spawk@128.238.9.199) by acm.poly.edu with AES256-SHA encrypted SMTP; 11 Aug 2009 20:06:38 -0000 Message-ID: <4A81CF20.7010108@acm.poly.edu> Date: Tue, 11 Aug 2009 16:05:52 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.19 (X11/20090108) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <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> <4A7C87C5.1070608@acm.poly.edu> <20090807202756.GB2487@garage.freebsd.pl> In-Reply-To: <20090807202756.GB2487@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS RAID-Z panic on vdev failure + subsequent panics and hangs 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: Tue, 11 Aug 2009 20:06:39 -0000 Pawel Jakub Dawidek wrote: > On Fri, Aug 07, 2009 at 04:00:05PM -0400, Boris Kochergin wrote: > >> 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. >> > > To get the data from there you could also try to 'zfs send' it without > mounting the dataset at all (just in case). > > Sorry for the delay. I had to find another machine to move the disks into so that I could continue experimenting. Anyway, the filesystem didn't have any snapshots I could send, so I tried creating one with "zfs snapshot home@1" and the machine hung. FYI, In the new machine, all disks (including the one with the / filesystem) retain their device names. -Boris