|0x01||Enable informational prints.|
|0x02||Enable tracing prints.|
|0x04||Enable prints for driver faults.|
|0x08||Enable prints for OCR and I/O timeout.|
|0x10||Enable prints for AEN events.|
The mrsas driver will always set a default (-30) priority in the PCI subsystem for selection of MR-Fusion cards. (It is between BUS_PROBE_DEFAULT and BUS_PROBE_LOW_PRIORITY). MR-Fusion Controllers include all cards with the Device IDs - 0x005B, 0x005D, 0x005F.
The mfi(4) driver will set a priority of either BUS_PROBE_DEFAULT or BUS_PROBE_LOW_PRIORITY (depending on the device.hints setting) in the PCI subsystem for selection of MR-Fusion cards. With the above design in place, the mfi(4) driver will attach to a MR-Fusion card given that it has a higher priority than mrsas.
Using /boot/device.hints (as mentioned below), the user can provide a preference for the mrsas driver to detect a MR-Fusion card instead of the mfi(4) driver.
.Cd hw.mfi.mrsas_enable= 1
At boot time, the mfi(4) driver will get priority to detect MR-Fusion controllers by default. Before changing this default driver selection policy, LSI advises users to understand how the driver selection policy works. LSIs policy is to provide priority to the mfi(4) driver to detect MR-Fusion cards, but allow for the ability to choose the mrsas driver to detect MR-Fusion cards.
LSI recommends setting hw.mfi.mrsas_enable="0" for customers who are using the older mfi(4) driver and do not want to switch to mrsas. For those customers who are using a MR-Fusion controller for the first time, LSI recommends using the mrsas driver and setting hw.mfi.mrsas_enable="1".
Changing the default behavior is well tested under most conditions, but unexpected behavior may pop up if more complex and unrealistic operations are executed by switching between the mfi(4) and mrsas drivers for MR-Fusion. Switching drivers is designed to happen only one time. Although multiple switching is possible, it is not recommended. The user should decide from Start of Day which driver they want to use for the MR-Fusion card.
The user may see different device names when switching from mfi(4) to mrsas. This behavior is Functions As Designed and the user needs to change the fstab(5) entry manually if they are doing any experiments with mfi(4) and mrsas interoperability.
/dev/da? array/logical disk interface /dev/mrsas? management interface
cam(4), mfi(4), pci(4), device.hints(5),
.Xt camcontrol 8
The mrsas driver first appeared in
.Fx 10.1 .
.Cd mfi Driver: mfi(4) is the old
.Fx driver which started with support for Gen-1 Controllers and was extended to support up to MR-Fusion (Device ID = 0x005B, 0x005D, 0x005F).
.Cd mrsas Driver: mrsas is the new driver reworked by LSI which supports Thunderbolt and onward products. The SAS+SATA RAID controller with device id 0x005b is referred to as the Thunderbolt controller throughout this man page.cam aware HBA drivers:
.Fx has a cam(4) layer which attaches storage devices and provides a common access mechanism to storage controllers and attached devices. The mrsas driver is cam(4) aware and devices associated with mrsas can be seen using camcontrol(8). The mfi(4) driver does not understand the cam(4) layer and it directly associates storage disks to the block layer.
Thunderbolt Controller: This is the 6Gb/s MegaRAID HBA card which has device id 0x005B.
Invader Controller: This is 12Gb/s MegaRAID HBA card which has device id 0x005D.
Fury Controller: This is the 12Gb/s MegaRAID HBA card which has device id 0x005F.
The mrsas driver and this manual page were written by
.An Kashyap Desai Aq Kashyap.Desai@lsi.com .
The driver does not support big-endian architectures at this time.
The driver does not support alias for device name (it is required when the user switches between two drivers and does not want to edit /etc/fstab manually).
The mrsas driver exposes devices as /dev/da?, whereas mfi(4) exposes devices as /dev/mfid?.
mrsas does not support the Linux Emulator interface.
mrsas will not work with mfiutil(8).