Date: Mon, 30 Sep 2019 15:59:02 -0400 From: "Dan Langille" <dan@langille.org> To: freebsd-scsi@freebsd.org Subject: mrsas/mfi : is /dev/megaraid_sas_ioctl_node just a proxy? Message-ID: <bfe1bf19-d761-4582-97ad-ff5cbd04bae5@www.fastmail.com>
next in thread | raw e-mail | index | archive | help
Hello, I'm working with the same hosts Wallace recently mentioned[1] but we one= remaining question. It seem that the the PERC H730P Mini (Embedded) SCSI card can present di= fferent devices depending upon the driver. We have the card in HBA mode. pciconf -lv sho= ws chip 0x005d100. man mrsas shows this is the Invader Controller. Our question is about a the /dev/megaraid_sas_ioctl_node symlink which s= eems to just point to the real driver. i.e. the symlink is a proxy If we put this in /boot/loader.conf: hw.mfi.mrsas_enable=3D"1" The symlink looks like: $ ls -l /dev/megaraid_sas_ioctl_node lrwxr-xr-x=C2=A0=C2=A01 root=C2=A0=C2=A0wheel=C2=A0=C2=A06 Sep 17 18:34 = /dev/megaraid_sas_ioctl_node -> mrsas0 This gives us da0 and da1 ... which is what we would expect (and want) b= ased on the man page. If we don't enable mrsas, we get this: $ ls -l /dev/megaraid_sas_ioctl_node lrwxr-xr-x=C2=A0=C2=A01 root=C2=A0=C2=A0wheel=C2=A0=C2=A04 Aug 23 19:25 = /dev/megaraid_sas_ioctl_node -> mfi0 Instead of da0/da1, we get mfisyspd0 & mfisyspd1 Is the symlink how the different drivers are invoked? We think we should use mrsas because it gives us the expected devices. W= e are mostly looking for wanted confirmation that we are not planting a long-term pro= blem.=20 Thank you --=20 Dan Langille dan@langille.org [1] - https://lists.freebsd.org/pipermail/freebsd-scsi/2019-September/00= 8028.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bfe1bf19-d761-4582-97ad-ff5cbd04bae5>