From owner-freebsd-fs@freebsd.org Fri Aug 11 08:09:29 2017 Return-Path: Delivered-To: freebsd-fs@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 2DB76DCA12B for ; Fri, 11 Aug 2017 08:09:29 +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 1B37665E3B for ; Fri, 11 Aug 2017 08:09:29 +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 v7B89SLs039157 for ; Fri, 11 Aug 2017 08:09:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219760] ZFS iSCSI w/ Win10 Initiator Causes pool corruption Date: Fri, 11 Aug 2017 08:09:29 +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: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emz@norma.perm.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@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-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 08:09:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219760 emz@norma.perm.ru changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emz@norma.perm.ru --- Comment #6 from emz@norma.perm.ru --- I observed similar behaviour on one of my SAN systems. In my opinion, iSCSI + zfs is broken somewhere between r310734 and r320056. Symptoms: - random fatal trap 12 panics. - random general protection faults panics - random "Solaris(panic): zfs: allocating allocated segment" panics - zfs pool corruption that happens ONLY on pools that serve the zvols as iS= CSI target devices - zfs pool corruption happening _on the fly_, without system panicking. - no zfs corruption is happening of the zfs pools not serving the devices f= or the iSCSI targets. I have 7 SAN systems running this setup. No system more recent than r310734= is showing that behaviour. The only system more recent than r310734 (at least r320056, and until 11.1-RELEASE) was affected by this, and became healthy w= hen downgraded to r310734 (r310734 was chosen simply because it's the most rece= nt revision on all of the 7). First I had the strong impression that we had a hardware problem. Memtest86+ found no problems. We found multiple SNART ATA errors that were caused by t= he bad cabling, and that seemed to be the rooy cause for the moment, but after switching to a new cable (and also to a new HBA, new server and new enclosu= re) the problem hasn't vanished. It was solved only after the downgrade to the r310734. The SAN system is up and running for 48 hours already without pool corruption (which usually happened withing first 12 hours of running) and without panics (which usually happened within first 24 hours). Unfortunately, I have no crashdumps, because the mpr(4) blocks crashdump collecting (see the discussion in the freebsd-scsi@). I have only the backtraces from serial-over-ethernet IPMI, which I will attach here. Problem initial description: https://lists.freebsd.org/pipermail/freebsd-fs/2017-August/025099.html --=20 You are receiving this mail because: You are the assignee for the bug.=