From owner-freebsd-fs@freebsd.org Mon Jun 5 19:33:25 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 883AFB79057 for ; Mon, 5 Jun 2017 19:33:25 +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 76D0F67337 for ; Mon, 5 Jun 2017 19:33:25 +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 v55JXPHi000353 for ; Mon, 5 Jun 2017 19:33:25 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: Mon, 05 Jun 2017 19:33:25 +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: henric_jungheim@yahoo.com 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: 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: Mon, 05 Jun 2017 19:33:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219760 --- Comment #3 from Henric Jungheim --- (In reply to Edward Tomasz Napierala from comment #2) The tank0 and tank0b drives are completely separate. Had I more sense when adding the two new drives, they would have been named something like "tankb= 0" and "tankb1". From "gpart show -l": =3D> 40 11721045088 ada3 GPT (5.5T) 40 2008 - free - (1.0M) 2048 11721041920 1 tank0b (5.5T) 11721043968 1160 - free - (580K) =3D> 40 11721045088 ada4 GPT (5.5T) 40 2008 - free - (1.0M) 2048 11721041920 1 tank1b (5.5T) 11721043968 1160 - free - (580K) =3D> 34 5860533101 da0 GPT (2.7T) 34 2014 - free - (1.0M) 2048 5860529032 1 tank0 (2.7T) 5860531080 2055 - free - (1.0M) =3D> 34 5860533101 da1 GPT (2.7T) 34 2014 - free - (1.0M) 2048 5860529032 1 tank1 (2.7T) 5860531080 2055 - free - (1.0M) Here's the gpart list for tank0 and tank1: Geom name: da0 modified: false state: OK fwheads: 255 fwsectors: 63 last: 5860533134 first: 34 entries: 128 scheme: GPT Providers: 1. Name: da0p1 Mediasize: 3000590864384 (2.7T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e2 rawuuid: 618bb5ab-66a1-11e2-8e33-00e081c81bd6 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: tank0 length: 3000590864384 offset: 1048576 type: freebsd-zfs index: 1 end: 5860531079 start: 2048 Consumers: 1. Name: da0 Mediasize: 3000592982016 (2.7T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e3 Geom name: da1 modified: false state: OK fwheads: 255 fwsectors: 63 last: 5860533134 first: 34 entries: 128 scheme: GPT Providers: 1. Name: da1p1 Mediasize: 3000590864384 (2.7T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e2 rawuuid: b0e34fe7-6a9e-11e2-8e33-00e081c81bd6 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: tank1 length: 3000590864384 offset: 1048576 type: freebsd-zfs index: 1 end: 5860531079 start: 2048 Consumers: 1. Name: da1 Mediasize: 3000592982016 (2.7T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e3 --=20 You are receiving this mail because: You are the assignee for the bug.=