From owner-freebsd-stable@FreeBSD.ORG Sun Dec 22 18:53:12 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 71237FD3 for ; Sun, 22 Dec 2013 18:53:12 +0000 (UTC) Received: from j006.host001.searchy.nl (j006.host001.searchy.nl [79.143.214.199]) by mx1.freebsd.org (Postfix) with ESMTP id 33C82110B for ; Sun, 22 Dec 2013 18:53:11 +0000 (UTC) Received: from [192.168.5.197] (5418287B.cm-5-1a.dynamic.ziggo.nl [84.24.40.123]) (Authenticated sender: ppi@j006.host001.searchy.nl) by j006.host001.searchy.nl (Postfix) with ESMTPSA id D75F01E8C07 for ; Sun, 22 Dec 2013 18:47:36 +0000 (UTC) Message-ID: <52B733C8.3030208@searchy.net> Date: Sun, 22 Dec 2013 19:47:36 +0100 From: "Frank de Bot (lists)" User-Agent: Mozilla/5.0 (X11; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: 10.0-RC2 kernel panic after removing iscsi target (zfs related) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Dec 2013 18:53:12 -0000 Hello, I just had a kernel panic on FreeBSD 10.0 RC2 while 'playing' around with iscsi and ZFS. The following steps lead to a kernel panic: - With the iscsi (native) initiator I tried to connect a ietd target. It connects and shows up as /dev/da0 - I try to create a single drive zpool: 'zpool create web004a /dev/da0' - It hangs and dmesg is spammed with: 'WARNING: 10.13.37.3:3260 (iqn.2013-12.nl.searchy.host003:web004a): connection error; reconnecting'. I didn't check any cause of this. - I tried to forcefully remove the iscsi drive with: 'iscsictl -R -t iqn.2013-12.nl.searchy.host003:web004a' - The kernel panic occurs. I can reproduce it with these steps. I don't have checked the target, but I think the iniator should not kernel panic if something goes wrong. Based on the backtrace I would guess it's ZFS related I have stored the crash information here: http://www.frankdebot.nl/freebsd/kernelpanic/20131222/core.txt.1 http://www.frankdebot.nl/freebsd/kernelpanic/20131222/info.1 Regards, Frank de Bot