From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 10 10:25:07 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED09A955 for ; Thu, 10 Jul 2014 10:25:07 +0000 (UTC) Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com [195.16.150.151]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA4E62A41 for ; Thu, 10 Jul 2014 10:25:06 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id C22859DCDBE; Thu, 10 Jul 2014 12:19:22 +0200 (CEST) Subject: Re: Data corruption with the mfi(4) driver Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20140710092251.GA1206@sekishi.zefyris.com> Date: Thu, 10 Jul 2014 12:19:21 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <3F26B4E0-2840-48AE-807B-FFFA4502DB83@sarenet.es> References: <20140710092251.GA1206@sekishi.zefyris.com> To: Francois Tigeot X-Mailer: Apple Mail (2.1283) Cc: FreeBSD-scsi X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2014 10:25:08 -0000 On Jul 10, 2014, at 11:22 AM, Francois Tigeot wrote: > Hi, >=20 > Now, this particular server was running under DragonFly and not = FreeBSD but > the mfi(4) driver is mostly the same under both operating systems and = I have > found reports of data corruption issues with mfi(4) and recent LSI = adapters > in the archives of this list. I reported data corruption affecting one of the new SAS3 controllers on = an IBM server. = http://lists.freebsd.org/pipermail/freebsd-scsi/2014-February/006260.html In my case, it happened when using the "passthrough" support (called = "syspd" or "jbod" by LSI). It did not corrupt data for me when using it as a RAID card. Cheers, Borja.