Data corruption with the mfi(4) driver

Steven Hartland killing at multiplay.co.uk
Thu Jul 10 10:36:34 UTC 2014


Your card is is based on 3108 chipset where as those lised in the dragonflybsd
report appear to be 2208 based, which is the same as what we're running here
without any issue, so I suspect the problems are unrelated.

I'm not sure if dragonflybsd imported our mfi fixes so they could well be
seeing the original issues.

    Regards
    Steve

----- Original Message ----- 
From: "Borja Marcos" <borjam at sarenet.es>
To: "Francois Tigeot" <ftigeot at wolfpond.org>
Cc: "FreeBSD-scsi" <freebsd-scsi at freebsd.org>
Sent: Thursday, July 10, 2014 11:19 AM
Subject: Re: Data corruption with the mfi(4) driver


> 
> On Jul 10, 2014, at 11:22 AM, Francois Tigeot wrote:
> 
>> Hi,
>> 
>> 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.
> 
> 
> 
> _______________________________________________
> freebsd-scsi at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe at freebsd.org"
>


More information about the freebsd-scsi mailing list