From owner-freebsd-stable@freebsd.org Wed Oct 14 21:25:59 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02AFDA15B72 for ; Wed, 14 Oct 2015 21:25:59 +0000 (UTC) (envelope-from lists@searchy.net) Received: from j006.host001.searchy.nl (j006.host001.searchy.nl [79.143.214.199]) by mx1.freebsd.org (Postfix) with ESMTP id BFF1B1259 for ; Wed, 14 Oct 2015 21:25:58 +0000 (UTC) (envelope-from lists@searchy.net) Received: from [192.168.5.21] (5418453B.cm-5-1b.dynamic.ziggo.nl [84.24.69.59]) (Authenticated sender: ppi@j006.host001.searchy.nl) by j006.host001.searchy.nl (Postfix) with ESMTPSA id 064891E8C07 for ; Wed, 14 Oct 2015 21:16:28 +0000 (UTC) Message-ID: <561EC629.30106@searchy.net> Date: Wed, 14 Oct 2015 23:16:25 +0200 From: "Frank de Bot (lists)" User-Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31 MIME-Version: 1.0 To: FreeBSD Stable Subject: Reloading iscsi target, iscsi initiator panics Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 21:25:59 -0000 Hello, I have a FreeBSD 10.2 server running as iSCSI target. Another FreeBSD 10.2 is an initiator and has several targets used. When I add a target and reload its config with 'service ctld reload', the FreeBSD initiator server panics. It's reproducable (I have a coredump, but I think it's clear what the problem is) How can I have the target reloads it config, without all initiators crashing? Right before the crash the iscsi session drops and reinits Regards, Frank de Bot Related dmesg from the initiator: Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): WRITE(10). CDB: 2a 00 00 29 93 c0 00 00 08 00 Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): CAM status: SCSI Status Error Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): SCSI status: Check Condition Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): SCSI sense: UNIT ATTENTION asc:3f,e (Reported LUNs data has changed) Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): Retrying command (per sense data) Oct 14 20:59:49 host004 kernel: da0 at iscsi1 bus 0 scbus7 target 0 lun 0 Oct 14 20:59:49 host004 kernel: da0: s/n MYSERIAL 2 detached Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): Periph destroyed Oct 14 20:59:49 host004 kernel: da0 at iscsi1 bus 0 scbus7 target 0 lun 0 Oct 14 20:59:49 host004 kernel: da0: Fixed Direct Access SPC-4 SCSI device Oct 14 20:59:49 host004 kernel: da0: Serial Number MYSERIAL 2 Oct 14 20:59:49 host004 kernel: da0: 150.000MB/s transfers Oct 14 20:59:49 host004 kernel: da0: Command Queueing enabled Oct 14 20:59:49 host004 kernel: da0: 20480MB (5242880 4096 byte sectors: 255H 63S/T 326C)