From owner-freebsd-scsi@freebsd.org Mon Oct 17 09:18:12 2016 Return-Path: Delivered-To: freebsd-scsi@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 C1638C15870 for ; Mon, 17 Oct 2016 09:18:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B04261BCD for ; Mon, 17 Oct 2016 09:18:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9H9ICte010031 for ; Mon, 17 Oct 2016 09:18:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Mon, 17 Oct 2016 09:18:12 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Feedback Timeout X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 09:18:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 Julien Cigar changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julien@perdition.city --- Comment #11 from Julien Cigar --- I got a similar issue on: FreeBSD filer1.prod.lan 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug= 11 18:38:15 UTC 2016=20=20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 with: root@filer1:/etc/rc.d # sysctl -a|grep -i 'iscsi' kern.iscsi.fail_on_shutdown: 1 kern.iscsi.fail_on_disconnection: 1 kern.iscsi.maxtags: 255 kern.iscsi.login_timeout: 5 kern.iscsi.iscsid_timeout: 5 kern.iscsi.ping_timeout: 5 kern.iscsi.debug: 1 On the initiator side: WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): no ping rep= ly (NOP-Out) after 5 seconds; dropping connection WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): connection error; dropping connection WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): connection error; dropping connection On the target side: WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting (da3:iscsi2:0:0:0): READ(10). CDB: 28 00 08 03 02 7a 00 00 01 00=20 (da3:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:(da2:iscsi1:0:0:0): READ(10). CDB: 28 00 02 d7 49 e7 00 00 20 00=20 iscsi2:0:(da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host 0:(da2:0): iscsi1:0:Retrying command 0:0): Retrying command (da3:iscsi2:0:0:0): READ(10). CDB: 28 00 02 d7 4a e7 00 00 20 00=20 (da2:iscsi1:0:0:0): READ(10). CDB: 28 00 02 d7 4a 07 00 00 20 00=20 (da3:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da3:(da2:iscsi2:0:iscsi1:0:0:0:0): 0): Retrying command Retrying command da3 at iscsi2 bus 0 scbus4 target 0 lun 0 da3: s/n MYSERIAL 1 detached da2 at iscsi1 bus 0 scbus3 target 0 lun 0 da2: s/n MYSERIAL 0 detached (da3:iscsi2:0:0:0): Periph destroyed (da2:iscsi1:0:0:0): Periph destroyed da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 1 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 0 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da3:iscsi1:0:0:0): READ(10). CDB: 28 00 02 d7 4c a7 00 00 20 00=20 (da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 02 e0 f3 d4 00 00 04 00=20 (da3:(da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host iscsi1:0:(da2:0:iscsi2:0:0): 0:Retrying command 0): Retrying command (da3:iscsi1:0:0:0): READ(10). CDB: 28 00 02 d7 4d 07 00 00 20 00=20 (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 02 d7 4b c7 00 00 20 00=20 (da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:(da2:iscsi1:0:iscsi2:0:0:0:0): 0): Retrying command Retrying command da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: s/n MYSERIAL 0 detached da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: s/n MYSERIAL 1 detached (da2:iscsi2:0:0:0): Periph destroyed (da3:iscsi1:0:0:0): Periph destroyed da2 at iscsi1 bus 0 scbus4 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 0 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) da3 at iscsi2 bus 0 scbus3 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 1 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting (da2:iscsi1:0:0:0): READ(6). CDB: 08 00 00 00 20 00=20 (da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi1:0:0:0): Retrying command (da2:iscsi1:0:0:0): READ(6). CDB: 08 00 00 10 02 00=20 (da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi1:0:0:0): Retrying command da2 at iscsi1 bus 0 scbus4 target 0 lun 0 da2: s/n MYSERIAL 0 detached (da2:iscsi1:0:0:0): Periph destroyed da2 at iscsi1 bus 0 scbus4 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 0 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da3:iscsi2:0:0:0): READ(6). CDB: 08 00 00 20 20 00=20 (da3:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:iscsi2:0:0:0): Retrying command da3 at iscsi2 bus 0 scbus3 target 0 lun 0 da3: s/n MYSERIAL 1 detached (da3:iscsi2:0:0:0): Periph destroyed WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting (da2:iscsi1:0:0:0): READ(6). CDB: 08 00 00 00 20 00=20 (da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi1:0:0:0): Retrying command da2 at iscsi1 bus 0 scbus4 target 0 lun 0 da2: s/n MYSERIAL 0 detached (da2:iscsi1:0:0:0): Periph destroyed da2 at iscsi1 bus 0 scbus3 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 0 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): login timed out after 6 seconds; reconnecting da3 at iscsi2 bus 0 scbus4 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 1 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting da2 at iscsi1 bus 0 scbus3 target 0 lun 0 da2: s/n MYSERIAL 0 detached (da2:iscsi1:0:0:0): READ(10). CDB: 28 00 1c 14 10 0f 00 00 01 00=20 (da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi1:0:0:0): Error 5, Periph was invalidated WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da3:iscsi2:0:0:0): READ(10). CDB: 28 00 1c 14 10 0f 00 00 01 00=20 (da3:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:iscsi2:0:0:0): Retrying command da3 at iscsi2 bus 0 scbus4 target 0 lun 0 da3: s/n MYSERIAL 1 detached (da2:iscsi1:0:0:0): Periph destroyed (da3:iscsi2:0:0:0): Periph destroyed da2 at iscsi1 bus 0 scbus4 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 0 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) da3 at iscsi2 bus 0 scbus3 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 1 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): handoff on already connected session Oct 16 01:02:04 filer1 iscsid[88600]: 10.20.30.32 (iqn.2016-08.lan.prod:target1): ISCSIDHANDOFF: Device busy WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): connection error; reconnecting da3 at iscsi2 bus 0 scbus3 target 0 lun 0 da3: s/n MYSERIAL 1 detached (da3:iscsi2:0:0:0): Periph destroyed da3 at iscsi2 bus 0 scbus3 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 1 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting (da2:iscsi1:0:0:0): READ(6). CDB: 08 00 00 20 20 00=20 (da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi1:0:0:0): Retrying command da2 at iscsi1 bus 0 scbus4 target 0 lun 0 da2: s/n MYSERIAL 0 detached (da2:iscsi1:0:0:0): Periph destroyed WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da3:iscsi2:0:0:0): READ(6). CDB: 08 00 00 20 20 00=20 (da3:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:iscsi2:0:0:0): Retrying command da3 at iscsi2 bus 0 scbus3 target 0 lun 0 da3: s/n MYSERIAL 1 detached (da3:iscsi2:0:0:0): Periph destroyed da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 1 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 0 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): connection error; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): connection error; reconnecting da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: s/n MYSERIAL 0 detached da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: s/n MYSERIAL 1 detached (da3:iscsi1:0:0:0): Periph destroyed (da2:iscsi2:0:0:0): Periph destroyed da2 at iscsi2 bus 0 scbus4 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 1 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) da3 at iscsi1 bus 0 scbus3 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 0 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Mon Oct 17 11:54:15 2016 Return-Path: Delivered-To: freebsd-scsi@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 3948FC154A9 for ; Mon, 17 Oct 2016 11:54:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 28C037DB for ; Mon, 17 Oct 2016 11:54:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9HBsEXZ035577 for ; Mon, 17 Oct 2016 11:54:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Mon, 17 Oct 2016 11:54:15 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Feedback Timeout X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 11:54:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #12 from Julien Cigar --- Some more info: on filer2: root@filer2:/home/jcigar # cat /etc/ctl.conf=20 auth-group ag0 { chap xxx xxx } portal-group pg0 { discovery-auth-group no-authentication listen 10.20.30.32 } target iqn.2016-08.lan.prod:target0 { auth-group ag0 portal-group pg0 lun 0 { blocksize 4096 path /dev/gpt/f2data0 } } target iqn.2016-08.lan.prod:target1 { auth-group ag0 portal-group pg0 lun 0 { blocksize 4096 path /dev/gpt/f2data1 } } root@filer2:/home/jcigar # ifconfig bge1 bge1: flags=3D8843 metric 0 mtu 9000 =20=20=20=20=20=20=20 options=3Dc019b ether d0:bf:9c:3a:b7:25 inet 10.20.30.32 netmask 0xffffff00 broadcast 10.20.30.255=20 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active root@filer2:/home/jcigar # pciconf -lv bge1 bge1@pci0:2:0:1: class=3D0x020000 card=3D0x22e8103c chip=3D0x165f14e= 4 rev=3D0x00 hdr=3D0x00 vendor =3D 'Broadcom Corporation' device =3D 'NetXtreme BCM5720 Gigabit Ethernet PCIe' class =3D network subclass =3D ethernet root@filer2:/home/jcigar # grep 'bge1' /var/run/dmesg.boot=20 bge1: mem 0x92b00000-0x92b0ffff,0x92b10000-0x92b1ffff,0x92b20000-0x92b2ffff at device= 0.1 on pci2 bge1: APE FW version: NCSI v1.3.12.0 bge1: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E miibus1: on bge1 bge1: Using defaults for TSO: 65518/35/2048 bge1: Ethernet address: d0:bf:9c:3a:b7:25 bge1: link state changed to DOWN bge1: link state changed to UP on filer1.prod.lan: root@filer1:/home/jcigar # cat /etc/iscsi.conf=20 t0 { TargetAddress =3D 10.20.30.32 TargetName =3D iqn.2016-08.lan.prod:target0 AuthMethod =3D CHAP chapIName =3D xxx chapSecret =3D xxx } t1 { TargetAddress =3D 10.20.30.32 TargetName =3D iqn.2016-08.lan.prod:target1 AuthMethod =3D CHAP chapIName =3D xxx chapSecret =3D xxx } root@filer1:/home/jcigar # ifconfig bge1 bge1: flags=3D8843 metric 0 mtu 9000 =20=20=20=20=20=20=20 options=3Dc019b ether d0:bf:9c:3a:c6:e1 inet 10.20.30.31 netmask 0xffffff00 broadcast 10.20.30.255=20 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active root@filer1:/home/jcigar # pciconf -lv bge1 bge1@pci0:2:0:1: class=3D0x020000 card=3D0x22e8103c chip=3D0x165f14e= 4 rev=3D0x00 hdr=3D0x00 vendor =3D 'Broadcom Corporation' device =3D 'NetXtreme BCM5720 Gigabit Ethernet PCIe' class =3D network subclass =3D ethernet root@filer1:/home/jcigar # grep 'bge1' /var/run/dmesg.boot=20 bge1: mem 0x92b00000-0x92b0ffff,0x92b10000-0x92b1ffff,0x92b20000-0x92b2ffff at device= 0.1 on pci2 bge1: APE FW version: NCSI v1.3.12.0 bge1: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E miibus1: on bge1 bge1: Using defaults for TSO: 65518/35/2048 bge1: Ethernet address: d0:bf:9c:3a:c6:e1 bge1: link state changed to DOWN bge1: link state changed to UP --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Tue Oct 18 09:20:08 2016 Return-Path: Delivered-To: freebsd-scsi@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 55D6CC1609F for ; Tue, 18 Oct 2016 09:20:08 +0000 (UTC) (envelope-from kashyap.desai@broadcom.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3013CC74 for ; Tue, 18 Oct 2016 09:20:08 +0000 (UTC) (envelope-from kashyap.desai@broadcom.com) Received: by mail-it0-x22d.google.com with SMTP id 139so67724785itm.1 for ; Tue, 18 Oct 2016 02:20:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc; bh=rgmtyna+0iVFT8I5mWsBOIwNDlQ4FBje8OwVvB3pWdI=; b=CW3FRNDvKWGmsDcHJLjZyNcp2lTwlCMYG4b9onyVvNdvwsTmyXsAGTuFjOEaZn0R+x 8xdZxwkWTB/Q8moSLoWWfneXJWi+pAScnUmAKmEdbdGGu7hSDPzml4/s11oIvFjbo1lU GqhMwM9A2gsCUWIgVp0O99H+gEVfkqDzfR0kw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc; bh=rgmtyna+0iVFT8I5mWsBOIwNDlQ4FBje8OwVvB3pWdI=; b=LAs2W4TPzBft2C0s11oAzfCEBW8YEw7rtwnX75tEF1mM1hX/dXBcwqzKKrGwZAE+Vi K6gSv38Z/mq/QP6SFsCMK/p1cpnugZe4E2vcu6BON0srAr1JQdmXx78mESS5xEZWudgO nnBmFTaT1kruVJWIvoHNUi03cH4M5BmpBnWvCR46SvnTmTCCTk/pl4Km8fgzHG5PY+9h DlzvodhvEEy/kzSew2Jv1QyAZpd5CcV6lVy0WV4AqNfPsJwv7O54aUZKb16X8xTMjI7p Oa5R7GAD+pcRXwEuOvie345PKAtA62sc1k27LWDTEC0abGT1gAyHRxu8FZ6seox190l/ uYig== X-Gm-Message-State: AA6/9RnX4rnYS2CgwYJ1XWvowNQpXDO7CYdowNl6RqUaCX4VjHCoMGPW97J6+UFgOu5F84M4YZ5P6V5sY6zQZtv9 X-Received: by 10.36.188.65 with SMTP id n62mr13317959ite.61.1476782407250; Tue, 18 Oct 2016 02:20:07 -0700 (PDT) From: Kashyap Desai References: <03ee30cfdb1ac86b644ff3516e0d88c0@mail.gmail.com> 2f1e12bf33bd90c4df3172294f20dc2e@mail.gmail.com 10b16ee77a11213da804bf8b0f2c58a0@mail.gmail.com In-Reply-To: 10b16ee77a11213da804bf8b0f2c58a0@mail.gmail.com MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHWPDlcg2acl0r0bM9EVuOrjfsiOqB+G5DQgB6Oc8CACR6IEA== Date: Tue, 18 Oct 2016 14:50:06 +0530 Message-ID: Subject: RE: MRSAS: SATA drives are getting deleted and then readded after controller reset To: Sumit Saxena , freebsd-scsi@freebsd.org, scott4long@yahoo.com, ken@freebsd.org Cc: Seema Kumashikar Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 09:20:08 -0000 Updated BZ - This issue is fixed using below patch. Please review and let me know if this is a correct fix. Root cause is - "Checksum is updated using different serial number. One without removing extra spaces and another with additional spaces. Because of that, any rescan of ATA disk is defected as different ATA drive, so it is removed and re-added later. " Index: scsi_xpt.c =================================================================== --- scsi_xpt.c (revision 307137) +++ scsi_xpt.c (working copy) @@ -1600,8 +1600,8 @@ sizeof(struct scsi_inquiry_data)); if (have_serialnum) - MD5Update(&context, serial_buf->serial_num, - serial_buf->length); + MD5Update(&context, path->device->serial_num, + path->device->serial_num_len); MD5Final(digest, &context); if (bcmp(softc->digest, digest, 16) == 0) Please review and let us know if we need fix in kernel or Any workaround to remove this check sum related code in CAM via some tunable ? ` Kashyap > -----Original Message----- > From: Kashyap Desai [mailto:kashyap.desai@broadcom.com] > Sent: Wednesday, October 12, 2016 7:33 PM > To: Sumit Saxena; 'freebsd-scsi@freebsd.org'; 'scott4long@yahoo.com'; > 'ken@freebsd.org' > Cc: Seema Kumashikar > Subject: RE: MRSAS: SATA drives are getting deleted and then readded after > controller reset > > Hi - > > Any update/pointer on this ? Issue happen only with SATA driver attached > via > CAM layer. > > Do we need to address this in driver or will there be any fix in CAM layer > ? > > > ` Kashyap > > > -----Original Message----- > > From: Kashyap Desai [mailto:kashyap.desai@broadcom.com] > > Sent: Friday, September 23, 2016 8:55 AM > > To: Sumit Saxena; 'freebsd-scsi@freebsd.org'; 'scott4long@yahoo.com'; > > 'ken@freebsd.org' > > Cc: Seema Kumashikar > > Subject: RE: MRSAS: SATA drives are getting deleted and then readded > > after controller reset > > > > Hi - > > > > I have posted new BZ/defect. > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212914 > > > > ~ Kashyap > > > > > -----Original Message----- > > > From: Sumit Saxena [mailto:sumit.saxena@broadcom.com] > > > Sent: Thursday, September 22, 2016 7:54 PM > > > To: freebsd-scsi@freebsd.org; scott4long@yahoo.com; ken@freebsd.org > > > Cc: Kashyap Desai; Seema Kumashikar > > > Subject: MRSAS: SATA drives are getting deleted and then readded > > > after controller reset > > > > > > Ken/Scott, > > > > > > On FreeBSD11.0 RC1, we are facing an issue where SATA drives > > > connected behind LSI's MegaRAID controller getting deleted and added > > > back after controller reset. > > > I am using Broadcom/Avago/LSI's MegaRAID Invader controller(device > > > ID- 0x005d). The point to note here is- this behavior is not > > > observed with SAS drives on FreeBSD11.0-RC1. > > > Also on FreeBSD10.3 this behavior is not at all observed on SATA as > > > well. > > > We are debugging the issue but it would be much helpful if we can > > > get quick inputs/pointers. > > > > > > Please find below the detailed information- > > > > > > OS: FreeBSD 11.0 RC1 > > > Controller: LSI's MegaRAID invader controller > > > > > > Connected devices list: > > > > > > root@freeBSD11:~ # camcontrol devlist > > > at scbus5 target 0 lun 0 > > > (pass0,ada0) > > > at scbus6 target 0 lun 0 > > > (ses0,pass1) > > > at scbus8 target 51 lun 0 > > > (da9,pass11)----------------------------------------->this is SATA > > > drive which is getting deleted and re-added post controller reset > > > at scbus8 target 163 lun 0 > > > (da8,pass10) > > > at scbus9 target 0 lun 0 > > > (da6,pass8) > > > at scbus9 target 1 lun 0 > > > (da2,pass4) > > > at scbus9 target 2 lun 0 > > > (da0,pass2) > > > at scbus9 target 3 lun 0 > > > (da7,pass9) > > > at scbus9 target 4 lun 0 > > > (da3,pass5) > > > at scbus9 target 5 lun 0 > > > (da1,pass3) > > > at scbus10 target 48 lun 0 > > > (da4,pass6) > > > at scbus10 target 54 lun 0 > > > (da5,pass7) > > > > > > > > > Relevant dmesg logs snippet(da9 is SATA drive which is getting > > > deleted and added back): > > > > > > ================================ > > > mrsas0: Initiaiting OCR because of FW fault! > > > mrsas0: Waiting for FW to come to ready state > > > mrsas0: Jbod map is supported > > > mrsas0: Reset successful > > > da9 at mrsas0 bus 1 scbus8 target 51 lun 0 > > > da9: s/n 9XE02AR2 detached > > > (da9:mrsas0:1:51:0): Periph destroyed > > > (da9:mrsas0:1:51:0): UNMAPPED > > > (da9:mrsas0:1:51:0): fatal error, could not acquire reference count > > > g_access(918): provider da9 has error > > > g_access(918): provider da9 has error > > > g_access(918): provider da9 has error > > > (da9:mrsas0:1:51:0): UNMAPPED > > > da9 at mrsas0 bus 1 scbus8 target 51 lun 0 > > > da9: Fixed Direct Access SPC-4 SCSI device > > > da9: Serial Number 9XE02AR2 > > > da9: 150.000MB/s transfers > > > da9: 238475MB (488397168 512 byte sectors) > > > ================================= > > > > > > Thanks, > > > Sumit From owner-freebsd-scsi@freebsd.org Tue Oct 18 13:57:24 2016 Return-Path: Delivered-To: freebsd-scsi@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 4DD6BC16123 for ; Tue, 18 Oct 2016 13:57:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D6C4661 for ; Tue, 18 Oct 2016 13:57:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9IDvOXA018583 for ; Tue, 18 Oct 2016 13:57:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Tue, 18 Oct 2016 13:57:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: trasz@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Feedback Timeout X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 13:57:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #13 from Edward Tomasz Napierala --- The "WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): no ping reply (NOP-Out) after 5 seconds; dropping connection" and "WARNING: 10.20.3= 0.32 (iqn.2016-08.lan.prod:target0): connection error; reconnecting" messages suggest a network problem. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Tue Oct 18 14:26:03 2016 Return-Path: Delivered-To: freebsd-scsi@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 4FA3DC16D37 for ; Tue, 18 Oct 2016 14:26:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 34BDAC13 for ; Tue, 18 Oct 2016 14:26:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9IEQ2f7019613 for ; Tue, 18 Oct 2016 14:26:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Tue, 18 Oct 2016 14:26:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Feedback Timeout X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 14:26:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #14 from Julien Cigar --- This is also what I thought at first, but there is no error messages relate= d to the network interfaces in the logs, and all Ierrs, Idrop, and Coll counters= are zeros. There is a dedicated interface for the iSCSI traffic which I turned on/off quite a lot to test a failover script, and the symptoms are exactly the ones described by Ben Rubson in the post above (altough I only have 4 disks in total). One more thing, I'm managing everything with SaltStack and in some cases ct= ld on the target and iscsid on the initiator are restarted at the same time, c= ould it be because of that? I forgot to paste my rc.conf filers, but I don't think there is something w= rong ..: root@filer1:/home/jcigar # cat /etc/rc.conf dumpdev=3D"AUTO" ifconfig_bge0=3D"DHCP" ip6addrctl_policy=3D"ipv4_prefer" ipv6_network_interfaces=3D"none" keymap=3D"be.iso" mountd_enable=3D"YES" mountd_flags=3D"-r -S -h 192.168.10.15" nfs_server_enable=3D"YES" nfs_server_flags=3D"-t -h 192.168.10.15" nfsuserd_enable=3D"YES" nfsuserd_flags=3D"-domain prod.lan" nfsv4_server_enable=3D"YES" ntpdate_flags=3D"-b -4" ntpdate_hosts=3D"ntp.belnet.be" salt_minion_enable=3D"YES" sendmail_enable=3D"NO" sendmail_msp_queue_enable=3D"NO" sendmail_outbound_enable=3D"NO" sendmail_submit_enable=3D"NO" zfs_enable=3D"YES" hostname=3D"filer1.prod.lan" ifconfig_bge1=3D"inet 10.20.30.31 netmask 255.255.255.0 mtu 9000" ifconfig_bge0_alias0=3D"inet vhid 54 advskew 50 pass xxx alias 192.168.10.1= 5/32" sshd_enable=3D"YES" ntpdate_enable=3D"YES" iscsid_enable=3D"YES" iscsictl_enable=3D"YES" iscsictl_flags=3D"-Aa" root@filer2:/home/jcigar # cat /etc/rc.conf dumpdev=3D"AUTO" ifconfig_bge0=3D"DHCP" ip6addrctl_policy=3D"ipv4_prefer" ipv6_network_interfaces=3D"none" keymap=3D"be.iso" ntpdate_flags=3D"-b -4" ntpdate_hosts=3D"ntp.belnet.be" salt_minion_enable=3D"YES" sendmail_enable=3D"NO" sendmail_msp_queue_enable=3D"NO" sendmail_outbound_enable=3D"NO" sendmail_submit_enable=3D"NO" zfs_enable=3D"YES" hostname=3D"filer2.prod.lan" ifconfig_bge1=3D"inet 10.20.30.32 netmask 255.255.255.0 mtu 9000" ifconfig_bge0_alias0=3D"inet vhid 54 advskew 100 pass xxx alias 192.168.10.= 15/32" sshd_enable=3D"YES" ntpdate_enable=3D"YES" ctld_enable=3D"YES" --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Tue Oct 18 14:34:37 2016 Return-Path: Delivered-To: freebsd-scsi@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 2A047C172A6 for ; Tue, 18 Oct 2016 14:34:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 196C5382 for ; Tue, 18 Oct 2016 14:34:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9IEYars038610 for ; Tue, 18 Oct 2016 14:34:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Tue, 18 Oct 2016 14:34:37 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ben.rubson@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 14:34:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 Ben RUBSON changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Closed |Open Resolution|Feedback Timeout |--- --- Comment #15 from Ben RUBSON --- I re-open this bug for Julien. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Tue Oct 18 14:54:30 2016 Return-Path: Delivered-To: freebsd-scsi@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 8A584C17B4F for ; Tue, 18 Oct 2016 14:54:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A2B3800 for ; Tue, 18 Oct 2016 14:54:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9IEsTjG078913 for ; Tue, 18 Oct 2016 14:54:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Tue, 18 Oct 2016 14:54:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 14:54:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #16 from Julien Cigar --- Thank you Ben. Can you confirm (once again) that you haven't had this probl= em anymore in 11.0-RELEASE? If so I could just upgrade then .. :) --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Tue Oct 18 15:02:04 2016 Return-Path: Delivered-To: freebsd-scsi@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 26CF5C17E56 for ; Tue, 18 Oct 2016 15:02:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 165DCF70 for ; Tue, 18 Oct 2016 15:02:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9IF23DL049625 for ; Tue, 18 Oct 2016 15:02:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Tue, 18 Oct 2016 15:02:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ben.rubson@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 15:02:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #17 from Ben RUBSON --- I switched to 11 at the time of 11-RC1 as I did not manage to reproduce the= bug with it. I did not try to explicitly reproduce it with RC2, RC3, 11.0-RELEASE and 11.0-RELEASE-p1, but it did not occur by itself in these versions :) Sounds like this bug only affects 10.3. --=20 You are receiving this mail because: You are on the CC list for the bug.=