From owner-freebsd-fs@FreeBSD.ORG Wed Aug 5 07:09:34 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 D6421106564A; Wed, 5 Aug 2009 07:09:34 +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 539AA8FC13; Wed, 5 Aug 2009 07:09:34 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:45611 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1MYacV-00069z-4O; Wed, 05 Aug 2009 09:09:09 +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 60EE318301B; Wed, 5 Aug 2009 09:09:03 +0200 (CEST) Message-Id: <7C3499A8-A389-4F28-A800-B6C31B9E09C4@exscape.org> From: Thomas Backman To: Pawel Jakub Dawidek In-Reply-To: <20090805065022.GI2181@garage.freebsd.pl> 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: Wed, 5 Aug 2009 09:09:01 +0200 References: <4A719CA4.4060400@freebsd.org> <19347561-3CE6-40B3-930A-EB9925D3AFD1@exscape.org> <4A71AD29.10705@freebsd.org> <7544AED1-1216-4A24-B287-F54117641F76@exscape.org> <4A71B239.8060007@freebsd.org> <3AA3C1CB-CEF7-46CC-A9C7-1648093D679E@exsca!pe.org> <4A71BED8.7050300@freebsd.org> <20090805065022.GI2181@garage.freebsd.pl> X-Mailer: Apple Mail (2.935.3) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1MYacV-00069z-4O. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MYacV-00069z-4O 72405053903911bc3b59f22783f4bf82 Cc: freebsd-fs@freebsd.org, FreeBSD current , Andriy Gapon Subject: Re: zfs: Fatal trap 12: page fault while in kernel mode 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: Wed, 05 Aug 2009 07:09:35 -0000 On Aug 5, 2009, at 08:50, Pawel Jakub Dawidek wrote: > On Fri, Jul 31, 2009 at 11:05:01AM +0200, Thomas Backman wrote: >> I'm able to reliably reproduce this panic, by having zfs recv destroy >> a filesystem on the receiving end. >> >> 1) Use DDEBUG=1, I guess >> 2) Create a FS on the source pool you don't care about: zfs create -o >> mountpoint=/testfs source/testfs >> 3) Clone a pool to another: zfs snapshot -r source@snap && zfs send >> -R >> source@snap | zfs recv -Fvd target >> 4) zfs destroy -r source/testfs >> 4) zfs snapshot -r source@snap2 && zfs send -R -I snap source@snap2 | >> zfs recv -Fvd target >> 5) ^ Panic while receiving the FS the destroyed one is mounted under. >> In my case, this was tank/root three times out of three; I then tried >> creating testfs under /tmp (tank/tmp/testfs), *mounting* it under / >> usr/ >> testfs, and it panics on receiving tank/usr: > [...] > > I repeated precisevly those steps and it doesn't panic for me. > Could you confirm that you use this patch? > > http://people.freebsd.org/~pjd/patches/zfs_vnops.c.2.patch > > If so, could you give me exact steps and all of them how to > reproduce it? > Starting with pool creation. Yup, I'm using that patch (I diffed the diffs, heh). I'll try to write a script to recreate the panic; I hope it's as easy as in real-world conditions though. Regards, Thomas