From owner-freebsd-scsi@freebsd.org Thu Feb 9 06:04:18 2017 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 BEECECD77D3 for ; Thu, 9 Feb 2017 06:04:18 +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 AED8C1DEF for ; Thu, 9 Feb 2017 06:04:18 +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 v1964Ipv049338 for ; Thu, 9 Feb 2017 06:04:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 216906] [iSCSI] Bad CRC may not be correctly handled Date: Thu, 09 Feb 2017 06:04:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: Thu, 09 Feb 2017 06:04:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216906 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-scsi@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-scsi@freebsd.org Sat Feb 11 04:56:05 2017 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 F06DFCD988F for ; Sat, 11 Feb 2017 04:56:05 +0000 (UTC) (envelope-from jwd@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D27E5186D for ; Sat, 11 Feb 2017 04:56:05 +0000 (UTC) (envelope-from jwd@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 821) id 2FD8D14FC; Sat, 11 Feb 2017 04:56:05 +0000 (UTC) Date: Sat, 11 Feb 2017 04:56:05 +0000 From: John To: FreeBSD-scsi Subject: multipath device never failing - loops over providers instead Message-ID: <20170211045605.GA43225@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline User-Agent: Mutt/1.7.1 (2016-10-04) 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: Sat, 11 Feb 2017 04:56:06 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Folks, Running 10.3-STABLE r308246 from Nov 3, 2016 I thought I saw a commit in this area a while back but I cannot seem to find it nor is google helping.. I have SAS drives behind 2 multiplexers (4 paths total) which are all configured similar to the following: # gmultipath status Z76 Name Status Components multipath/Z76 OPTIMAL da92 (ACTIVE) da236 (PASSIVE) da428 (PASSIVE) da572 (PASSIVE) For each path on the components above, the following sequence occurs: kernel: (da92:mpr0:0:399:0): READ(10). CDB: 28 00 0b a7 20 c0 00 00 10 00= =20 kernel: (da92:mpr0:0:399:0): CAM status: SCSI Status Error kernel: (da92:mpr0:0:399:0): SCSI status: Check Condition kernel: (da92:mpr0:0:399:0): SCSI sense: HARDWARE FAILURE asc:32,0 (No defe= ct spare location available) kernel: (da92:mpr0:0:399:0): Info: 0xba720c0 kernel: (da92:mpr0:0:399:0): Field Replaceable Unit: 157 kernel: (da92:mpr0:0:399:0): Command Specific Info: 0x80010000 kernel: (da92:mpr0:0:399:0): Actual Retry Count: 255 kernel: (da92:mpr0:0:399:0): Retrying command (per sense data) After each path has failed, the following is seen: kernel: GEOM_MULTIPATH: Error 5, da92 in Z76 marked FAIL kernel: GEOM_MULTIPATH: all paths in Z76 were marked FAIL, restore da572 kernel: GEOM_MULTIPATH: all paths in Z76 were marked FAIL, restore da428 kernel: GEOM_MULTIPATH: all paths in Z76 were marked FAIL, restore da236 kernel: GEOM_MULTIPATH: da572 is now active path in Z76 and the entire failure loop occurs again. The multipath device itself is never failed (so the zfs pool can never go into degraded mode, the faulty drive replaced with a spare, etc). Once I pulled the drive the multipath device Z76 fails and things sent as expected. It seems g_multipath_fault() in this instance should just fail the devic= e. Does anyone have any pointers on this issue? Thanks, John --17pEHd4RhPHOinZp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQF8BAEBCgBmBQJYnpljXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNDBGOTgxNzM0NzQ3OEFBNDYyODNGQzVC NjI0OTlBMTQyNEY3RjgxAAoJELYkmaFCT3+BGk4IALskuVHIvoVBhLkuAViD8/ME i/LckUyVRB86r5lHoetAfPo8yQv7urAMvB27PBnvDRsxKWF/aCMxioVHjFsai86R BpsObFYycGazAoEgoxYsybs5wtKGO5pLm+VPS8DSaHHiNmJtpFeEg8a1vLhdOCmj IpZHyo5StiUokvde3TViAHUo3+CeBVir5K63QlqelHtNa1oE/0difiJfkogdioHs EBCQ34NqzsbGbogo0O8ubKI77LYZnsIxn49z0pMIoXohxuCpw53PCoN+QuFCmrjp 9n5GtA5crOieE2pixEUuixJzT1s+/6ZTeV0IaFRn7I0WZpTqsWSmspnZorOuwUk= =KkTg -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--