From owner-freebsd-bugs@freebsd.org Mon Aug 12 13:34:34 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3DD4BB3CF2 for ; Mon, 12 Aug 2019 13:34:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 466cJp0sZZz4MHC for ; Mon, 12 Aug 2019 13:34:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 1DAB5B3CF1; Mon, 12 Aug 2019 13:34:34 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1D714B3CF0 for ; Mon, 12 Aug 2019 13:34:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 466cJp00pgz4MHB for ; Mon, 12 Aug 2019 13:34:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D67BB274DD for ; Mon, 12 Aug 2019 13:34:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7CDYXU4030806 for ; Mon, 12 Aug 2019 13:34:33 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7CDYX0E030805 for bugs@FreeBSD.org; Mon, 12 Aug 2019 13:34:33 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239801] mfi errors causing zfs checksum errors Date: Mon, 12 Aug 2019 13:34:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mafua@dempseyuniform.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Aug 2019 13:34:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239801 Bug ID: 239801 Summary: mfi errors causing zfs checksum errors Product: Base System Version: 11.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: mafua@dempseyuniform.com After upgrading to FreeBSD 11.3 I began having storage issues. (I may have experienced the same problem when testing FreeBSD 12.0). At first I though= t it was a problem with upgrading my ZFS pool to include the update for spacemap= _v2, but now I think it's a lower level problem. After a day or two, I start to= see checksum errors appear on a pool. Doing a scrub on the pool just results in more errors. If I restart the machine, I can then scrub the pool and errors= no longer appear, then after a few days it happens again. There's only one or two machines I haven't upgraded my zpool on, but I think it's just a coincidence that I saw the problem after upgrading the zpool (thinking the upgrade went okay). But I haven't experienced problems on the= one machine I haven't upgraded the pool on. All (3) servers are Dell PowerEdge servers, using a PERC raid controller configured as JBOD. They have two drives configured as a zfs mirror. One machine had a drive failure a few months ago, which was replaced and running fine, but otherwise all machines have been running for years with no issues= and never failed a scrub until the upgrade. They're at different locations, so = that probably rules out power issues. mfi0 Adapter: Product Name: PERC H330 Adapter Serial Number: 59N01F6 Firmware: 25.3.0.0016 RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID10, RAID50 Battery Backup: not present NVRAM: 32K Onboard Memory: 0M Minimum Stripe: 64K Maximum Stripe: 64K mfi0 Physical Drives: 0 ( 932G) JBOD SCSI-6 S0 1 ( 932G) JBOD SCSI-6 S1 Errors Reported in /var/log/messages kernel: mfi0: I/O error, cmd=3D0xfffffe0000f9a4a8, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 0, sense_key 0, asc 0, ascq 0 kernel: mfisyspd1: hard error cmd=3Dwrite 675298440-675298991 kernel: mfi0: I/O error, cmd=3D0xfffffe0000f99dc0, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 0, sense_key 0, asc 0, ascq 0 kernel: mfisyspd1: hard error cmd=3Dwrite 675298504-675299015 kernel: mfi0: I/O error, cmd=3D0xfffffe0000f9c048, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 0, sense_key 0, asc 0, ascq 0 kernel: mfisyspd0: hard error cmd=3Dwrite 675298504-675299015 kernel: mfi0: I/O error, cmd=3D0xfffffe0000f9ae38, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 0, sense_key 0, asc 0, ascq 0 kernel: mfisyspd0: hard error cmd=3Dwrite 675298440-675298991 kernel: mfi0: I/O error, cmd=3D0xfffffe0000f9c048, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 0, sense_key 0, asc 0, ascq 0 kernel: mfisyspd0: hard error cmd=3Dwrite 675298440-675298991 kernel: mfi0: I/O error, cmd=3D0xfffffe0000f9afd0, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 0, sense_key 0, asc 0, ascq 0 kernel: mfisyspd1: hard error cmd=3Dwrite 675298440-675298991 kernel: mfi0: I/O error, cmd=3D0xfffffe0000f98bb0, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 47, sense_key 15, asc 175, ascq 175 kernel: mfisyspd1: hard error cmd=3Dwrite 675298440-675298991 kernel: mfi0: I/O error, cmd=3D0xfffffe0000f9a6c8, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 0, sense_key 0, asc 0, ascq 0 kernel: mfisyspd0: hard error cmd=3Dwrite 675298440-675298991 kernel: mfi0: I/O error, cmd=3D0xfffffe0000f9b0e0, status=3D0x3c, scsi_stat= us=3D0 kernel: mfi0: sense error 0, sense_key 0, asc 0, ascq 0 kernel: mfisyspd0: hard error cmd=3Dwrite 675298440-675298991 --=20 You are receiving this mail because: You are the assignee for the bug.=