Date: Wed, 04 Sep 2019 02:09:47 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239801] mfi errors causing zfs checksum errors Message-ID: <bug-239801-227-y9Nq0udf82@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239801-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239801-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239801 Hiroki Sato <hrs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress --- Comment #5 from Hiroki Sato <hrs@FreeBSD.org> --- (In reply to Daniel Mafua from comment #4) Thanks for your report. I have several other systems which are suffering f= rom the same problem. Here is information about this problem which I got so fa= r: * mfi(4) can report I/O errors which is not related to an actual hardware failure after upgrading FreeBSD to 11.3 or 12.0. * The error does not depend on ZFS while ZFS is very likely to report checksum errors of the zpool. On a system using UFS, the I/O error can cause a system panic, boot failure, or something fatal. * It seems that the I/O error depends on a specific firmware version. Some older firmware versions work fine even with mfi(4) on 11.3 and 12.0.=20 * If the device is also supported by mrsas(4), switching to it will solves the error. Note that it will cause an incompatibility issue---mfi(4) uses /dev/mfi* device nodes for the attached drives and mfiutil(8) as the user= land utility. mrsas(4) uses /dev/da* and a vendor-supplied utility such as megaCli instead. I am investigating what caused this regression but a workaround is to use mrsas(4) instead of mfi(4) by specifying hw.mfi.mrsas_enable=3D"1" at boot = time. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239801-227-y9Nq0udf82>