LSI - MR-Fusion controller driver <mrsas> patch and man page

[Borja Marcos]

On Mar 21, 2014, at 5:09 PM, Doug Ambrisko wrote:

> Do you have a simple test case for that?  There were issues in the SCSI
> command translation which should have been fixed via switching it to use
> the CAM translation code.  Can you try it via a RAID volume of one disk?

Yes, I tried all those possibilities. "syspd" devices, passthrough (same result, corrruption) and
when creating single-disk RAID0 volumes it worked, no corruption.

Just in case I tried with SSDs (Samsung EVO  840 and OCZ Vertex 4) and Seagate SAS disks.

> | The server is not in production, so I have no problems to try drivers, etc.
> 
> You could try the LSI mrsas and see if the corruption goes away and then
> we could try to isolate the difference.  mrsas does not support CAM
> passthrough.  If both drivers are loaded in the kernel, you can prevent
> mfi from attaching and let mrsas attach via the tunable:
> 	hw.mfi.mrsas_enable=1
> The mrsas device come up /dev/da* there are no aliases yet to the mfi one's.
> Also mfiutil won't work with mrsas but MegaCli/StorCli should.  If you want
> to use mfiutil, you can switch to mfi to set that up and then switch back
> to mrsas.  I need to finish the mrsas compat work so mfiutil can work
> on it.  It's a little more complicated then I hoped.

Actually I think that converting passthrough disks to "mfisyspd" or an equivalent is a bad idea,
unless, of course, there's a compelling reason I don't realize. For instance, if you are using
SSDs you need access to the TRIM command.

So, if I can vote, I vote with arms and legs for "da" devices in case it's a passthough.

It's not a pressing need, I installed a LSI2008 card and I connected the SAS backplane to it, so for now the Invader
is a non-problem, but if it will help to run some tests with the mps driver I can certainly do it.





Borja.