From owner-freebsd-current@FreeBSD.ORG Fri Jun 5 14:18:12 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 65EB8106566B; Fri, 5 Jun 2009 14:18:12 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id E335B8FC1A; Fri, 5 Jun 2009 14:18:11 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:53893 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.69) (envelope-from ) id 1MCaEu-0001sa-3f; Fri, 05 Jun 2009 16:17:50 +0200 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id 096EC122AC9; Fri, 5 Jun 2009 16:17:47 +0200 (CEST) Message-Id: <3AB9BCA0-DCEA-4E64-A01D-8BA9B75C3ECD@exscape.org> From: Thomas Backman To: Kip Macy In-Reply-To: <3c1674c90905211131q607e05a9m68e906f2d3620414@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Fri, 5 Jun 2009 16:17:44 +0200 References: <20090518145614.GF82547@egr.msu.edu> <3c1674c90905181659g1d20f0f1w3f623966ae4440ec@mail.gmail.com> <3c1674c90905181800x469d3cabx5df959d3585b4b5a@mail.gmail.com> <040ce5cee10b3b92fd127bbce83f4c77.squirrel@webmail.lerctr.org> <3c1674c90905181815r49a5bbe2u5d4a73e4f91f89a6@mail.gmail.com> <3c1674c90905211131q607e05a9m68e906f2d3620414@mail.gmail.com> X-Mailer: Apple Mail (2.935.3) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1MCaEu-0001sa-3f. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MCaEu-0001sa-3f d1726a8252c16b192e1f5c4615331e96 Cc: FreeBSD Current Subject: Re: Fatal trap 12: page fault panic with recent kernel with ZFS 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: Fri, 05 Jun 2009 14:18:12 -0000 On May 21, 2009, at 08:31 PM, Kip Macy wrote: >> Hey, I (not the OP) am still having trouble with this. The panics >> appear to >> be gone since I set arc_min to 30M and arc_max to 100M, though (2GB >> RAM). >> I get/got them during a full zfs send -R | zfs recv -Fvd of a >> ~3.3GB pool. >> The only modification I've done to the source tree is the >> libzfs_sendrecv >> patch here: >> http://lists.freebsd.org/pipermail/freebsd-current/2009-May/006814.html > > > I'll apply the patch this weekend. > > If I get time I'll also try to reproduce your panic. > > > Thanks, > Kip Two weekends later and still the same deal with send | recv. ;) Just worried that this'll make it into 8.0-RELEASE, that's all. That would be bad. The patch linked above seems to solve the problem for me, anyway. I just tried a fresh build (sources from June 5th at 10AM CEST), without the patch, and I got the same core dump on zfs recv, with a SIGSEGV in strcmp(). (See the linked thread.) Applied the patch, rebuild libzfs, rebooted, and it works again. It seems something along the lines of zfs snapshot -r tank@initial-snapshot zfs send -R tank@initial-snapshot | zfs recv -vFd slave and then zfs snapshot -r tank@testsnap # some other, unrelated snapshot in between may or may not be needed to crash, I'm not sure zfs snapshot -r tank@second-snapshot zfs send -R -I initial-snapshot tank@second-snapshot | zfs recv -Fvd slave causes the core dump. Regards, Thomas