From owner-freebsd-fs@freebsd.org Sat Jun 10 22:52:33 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 14942BF7CE0 for ; Sat, 10 Jun 2017 22:52:33 +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 ECEEE65A3D for ; Sat, 10 Jun 2017 22:52:32 +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 v5AMqW4T021373 for ; Sat, 10 Jun 2017 22:52:32 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: Sat, 10 Jun 2017 22:52:33 +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: Sat, 10 Jun 2017 22:52:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219760 --- Comment #5 from Henric Jungheim --- (In reply to Edward Tomasz Napierala from comment #4) The ada4 and ada3 disks were added because the existing mirror set in the p= ool was full (as in "getting out of disk space errors", not "uncomfortably high= "), so they are not likely to see any significant writes. This is a home NAS s= etup and while I have backups in the cloud and some on LTO3 tapes, I don't have anywhere local I can store what is on those drives so I'm really reluctant = to pull those drives. I was not able to find any firmware updates for those drives. Both long and short SMART tests have been run w/o finding anything. Writing multiple 1TB files to files with "dd if=3D/dev/random" hasn't caused any problems. I'll= try doing those "dd"s to zdevs next. The "write a couple TB, then scrub," test= ing takes a while; any thoughts on other non-destructive testing I could do? Is there some sane way to get a list of what the actual errors are in the p= ool (offset on the raw disk or such)? When I've done the backup, both drives h= ave always reported the same number of errors. If both drives report exactly t= he same (bad) data at the same locations, then that could perhaps suggest something useful? I have both the chipset SATA ports and SAS/SATA ports from the motherboards= LSI SAS controller. I might be able to move the drives from one controller to = the other. Another device--a Server 2008 R2 box--has been doing similar iSCSI backups = to another pool in the system for years. It, however, has much less to write = and does so from spinning rust instead of SSD (although, I would assume the GigE link is still the bottleneck). The drives for this other pool are on the s= ame controller as ada3 and ada4. I'll see about having it do an extra backup or two to the "tank" pool to see if it causes any grief there. For ada3: smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.1-PRERELEASE amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D Model Family: HGST Deskstar NAS Device Model: HGST HDN726060ALE610 Serial Number: NCGTEJ2S LU WWN Device Id: 5 000cca 24dcb1ba7 Firmware Version: APGNT517 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sat Jun 10 15:49:55 2017 MST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Disabled Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Enabled =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D SMART overall-health self-assessment test result: PASSED For ada4: smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.1-PRERELEASE amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D Model Family: HGST Deskstar NAS Device Model: HGST HDN726060ALE610 Serial Number: NCGTES1S LU WWN Device Id: 5 000cca 24dcb1c7f Firmware Version: APGNT517 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sat Jun 10 15:46:34 2017 MST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Disabled Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Enabled =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D SMART overall-health self-assessment test result: PASSED --=20 You are receiving this mail because: You are the assignee for the bug.=