Discussion:
Dell Shared PERC8 RAID Controller
Istvan Hubay Cebrian
2014-03-03 14:53:36 UTC
Permalink
Hello,

Am sending this email here as I think it is possibly the most
appropriate place. If not, please disregard/ignore and my apologizes.

Recently I have bought a new Dell PowerEdge VRTX Enclosure
(http://www.dell.com/us/business/p/poweredge-vrtx/pd) that houses Dell
PowerEdge M520 Blade server
(http://www.dell.com/us/business/p/poweredge-m520/pd).

This solution (http://bladesmadesimple.com/2013/06/a-detailed-look-at-dell-poweredge-vrtx/),
released specifically for the SMB market currently only works with
Windows Server 2008+ and VMware ESXi.

This due to a controller called the Shared PERC8 RAID Controller
(http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=7HPN0)
which apparently is not supported in Linux.

I have been trying to get feedback from Dell for nearly 1 year now but
to no avail. Dell say's it is not supported and that it is the
community that needs to provide the drivers first. When I asked if
they where providing support to the community I never received a
response.

What I don't understand is how VMware ESXi which I believe uses the
Linux Kernel is already supported and it can work with said
controller. Possibly because it does not use MegaRAID drivers? Not
sure.

This email is either to discuss this matter further or aimed at
requesting support for the Dell Shared PERC8 RAID Controller in order
to allow such platforms as the VRTX and enable SMB all the advantages
of using this hardware coupled with Linux thus allowing for a very
budget friendly infrastructure.

lspci -nn (on Dell PowerEdge M520 Blade)
...
01:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID
SAS 2008 [Falcon] [1000:0073] (rev 03)
08:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID
SAS 2208 IOV [Thunderbolt] [1000:002f] (rev 05)
...

Sincerely,
--
Istvan Hubay Cebrian
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Emmanuel Florac
2014-03-03 15:09:44 UTC
Permalink
Le Mon, 3 Mar 2014 14:53:36 +0000
Post by Istvan Hubay Cebrian
lspci -nn (on Dell PowerEdge M520 Blade)
...
01:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAI=
D
Post by Istvan Hubay Cebrian
SAS 2008 [Falcon] [1000:0073] (rev 03)
This one is supported by the megaraid_sas driver, provided it's recent
enough.=20
Post by Istvan Hubay Cebrian
08:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAI=
D
Post by Istvan Hubay Cebrian
SAS 2208 IOV [Thunderbolt] [1000:002f] (rev 05)
...
This one seems unsupported. I don't know what it's actually for,
though. Is it the one posing you a problem? I suppose ESXi lets you
check (with modinfo) if megaraid_sas manages it.

--=20
-----------------------------------------------------------------------=
-
Emmanuel Florac | Direction technique
| Intellique
| <***@intellique.com>
| +33 1 78 94 84 02
-----------------------------------------------------------------------=
-
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Istvan Hubay Cebrian
2014-03-03 15:22:13 UTC
Permalink
I can't tell you exactly which one is causing me problems but I can
assume it is the unsupported one.

Basically the M520 Blades also have internal storage. I can see and
mount that storage.

[***@hostname ~]# lsmod | grep raid
megaraid_sas 87177 2

[***@hostname ~]# modinfo megaraid_sas
filename:
/lib/modules/2.6.32-431.5.1.el6.x86_64/kernel/drivers/scsi/megaraid/meg=
araid_sas.ko
description: LSI MegaRAID SAS Driver
author: ***@lsi.com
version: 06.700.06.00-rh1
license: GPL
srcversion: 9426C5CDA69586AABE13C02
alias: pci:v00001000d0000005Fsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Dsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Bsv*sd*bc*sc*i*
alias: pci:v00001028d00000015sv*sd*bc*sc*i*
alias: pci:v00001000d00000413sv*sd*bc*sc*i*
alias: pci:v00001000d00000071sv*sd*bc*sc*i*
alias: pci:v00001000d00000073sv*sd*bc*sc*i*
alias: pci:v00001000d00000079sv*sd*bc*sc*i*
alias: pci:v00001000d00000078sv*sd*bc*sc*i*
alias: pci:v00001000d0000007Csv*sd*bc*sc*i*
alias: pci:v00001000d00000060sv*sd*bc*sc*i*
alias: pci:v00001000d00000411sv*sd*bc*sc*i*
depends:
vermagic: 2.6.32-431.5.1.el6.x86_64 SMP mod_unload modversions
parm: max_sectors:Maximum number of sectors per IO command (i=
nt)
parm: msix_disable:Disable MSI-X interrupt handling. Default:=
0 (int)
parm: msix_vectors:MSI-X max vector count. Default: Set by FW=
(int)
parm: throttlequeuedepth:Adapter queue depth when throttled
due to I/O timeout. Default: 16 (int)
parm: resetwaittime:Wait time in seconds after I/O timeout
before resetting adapter. Default: 180 (int)
I can't however see the Shared storage provided by the VRTX Enclosure.
I would assume one controller is for the internal storage of the M520
Blade and the other controller for the Shared storage.

--
Istvan Hubay Cebrian
http://icebrian.net
Post by Emmanuel Florac
Le Mon, 3 Mar 2014 14:53:36 +0000
Post by Istvan Hubay Cebrian
lspci -nn (on Dell PowerEdge M520 Blade)
...
01:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRA=
ID
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
SAS 2008 [Falcon] [1000:0073] (rev 03)
This one is supported by the megaraid_sas driver, provided it's rece=
nt
Post by Emmanuel Florac
enough.
Post by Istvan Hubay Cebrian
08:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRA=
ID
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
SAS 2208 IOV [Thunderbolt] [1000:002f] (rev 05)
...
This one seems unsupported. I don't know what it's actually for,
though. Is it the one posing you a problem? I suppose ESXi lets you
check (with modinfo) if megaraid_sas manages it.
--
---------------------------------------------------------------------=
---
Post by Emmanuel Florac
Emmanuel Florac | Direction technique
| Intellique
| +33 1 78 94 84 02
---------------------------------------------------------------------=
---
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Emmanuel Florac
2014-03-03 15:33:17 UTC
Permalink
Le Mon, 3 Mar 2014 15:22:13 +0000
I can't however see the Shared storage provided by the VRTX Enclosure=
=2E
I would assume one controller is for the internal storage of the M520
Blade and the other controller for the Shared storage.
Yes, that's probably the case. As I said, I'd first try installing ESXi
on a blade to check what driver it uses for this particular card (ESXi
is a special Linux distro after all).

--=20
-----------------------------------------------------------------------=
-
Emmanuel Florac | Direction technique
| Intellique
| <***@intellique.com>
| +33 1 78 94 84 02
-----------------------------------------------------------------------=
-
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Istvan Hubay Cebrian
2014-03-03 16:57:44 UTC
Permalink
So I do have ESXi on one of the blade servers. Curiously "lspci -nn"
output is very different. I for example don't see two RAID controllers
but one:

=2E..
00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic
53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
=2E..

Also, lsmod returns the following:

[***@storpro ~]# lsmod
Module Size Used by
nfsd 304902 13
lockd 73534 1 nfsd
nfs_acl 2647 1 nfsd
auth_rpcgss 44917 1 nfsd
autofs4 26449 3
sunrpc 261235 19 nfsd,lockd,nfs_acl,auth_rpcgss
ipv6 321582 68
xfs 1088447 2
exportfs 4236 2 nfsd,xfs
ppdev 8537 0
parport_pc 22690 0
parport 36209 2 p[***@storpro ~]# lsmod
Module Size Used by
nfsd 304902 13
lockd 73534 1 nfsd
nfs_acl 2647 1 nfsd
auth_rpcgss 44917 1 nfsd
autofs4 26449 3
sunrpc 261235 19 nfsd,lockd,nfs_acl,auth_rpcgss
ipv6 321582 68
xfs 1088447 2
exportfs 4236 2 nfsd,xfs
ppdev 8537 0
parport_pc 22690 0
parport 36209 2 ppdev,parport_pc
e1000 170678 0
microcode 112653 0
vmware_balloon 7199 0
sg 29350 0
i2c_piix4 12608 0
i2c_core 31084 1 i2c_piix4
shpchp 32778 0
ext4 363344 2
jbd2 91554 1 ext4
mbcache 8193 1 ext4
sd_mod 38976 7
crc_t10dif 1541 1 sd_mod
sr_mod 15177 0
cdrom 39085 1 sr_mod
mptspi 16603 4
mptscsih 36700 1 mptspi
mptbase 93647 2 mptspi,mptscsih
scsi_transport_spi 25863 1 mptspi
pata_acpi 3701 0
ata_generic 3837 0
ata_piix 24121 0
dm_mirror 14133 0
dm_region_hash 12085 1 dm_mirror
dm_log 9930 2 dm_mirror,dm_region_hash
dm_mod 82839 8 dm_mirror,dm_log
pdev,parport_pc
e1000 170678 0
microcode 112653 0
vmware_balloon 7199 0
sg 29350 0
i2c_piix4 12608 0
i2c_core 31084 1 i2c_piix4
shpchp 32778 0
ext4 363344 2
jbd2 91554 1 ext4
mbcache 8193 1 ext4
sd_mod 38976 7
crc_t10dif 1541 1 sd_mod
sr_mod 15177 0
cdrom 39085 1 sr_mod
mptspi 16603 4
mptscsih 36700 1 mptspi
mptbase 93647 2 mptspi,mptscsih
scsi_transport_spi 25863 1 mptspi
pata_acpi 3701 0
ata_generic 3837 0
ata_piix 24121 0
dm_mirror 14133 0
dm_region_hash 12085 1 dm_mirror
dm_log 9930 2 dm_mirror,dm_region_hash
dm_mod 82839 8 dm_mirror,dm_log

[***@storpro ~]# modinfo mptspi
filename:
/lib/modules/2.6.32-358.18.1.el6.x86_64/kernel/drivers/message/fusion/m=
ptspi.ko
version: 3.04.20
license: GPL
description: Fusion MPT SPI Host driver
author: LSI Corporation
srcversion: BFB86D57259351D6A601FFB
alias: pci:v00001000d00000040sv*sd*bc*sc*i*
alias: pci:v0000117Cd00000030sv*sd*bc*sc*i*
alias: pci:v00001000d00000030sv*sd*bc*sc*i*
depends: mptscsih,scsi_transport_spi,mptbase
vermagic: 2.6.32-358.18.1.el6.x86_64 SMP mod_unload modversions
parm: mpt_saf_te: Force enabling SEP Processor: enable=3D1
(default=3DMPTSCSIH_SAF_TE=3D0) (int)
--
Istvan Hubay Cebrian
http://icebrian.net
Post by Emmanuel Florac
Le Mon, 3 Mar 2014 15:22:13 +0000
I can't however see the Shared storage provided by the VRTX Enclosur=
e.
Post by Emmanuel Florac
I would assume one controller is for the internal storage of the M52=
0
Post by Emmanuel Florac
Blade and the other controller for the Shared storage.
Yes, that's probably the case. As I said, I'd first try installing ES=
Xi
Post by Emmanuel Florac
on a blade to check what driver it uses for this particular card (ESX=
i
Post by Emmanuel Florac
is a special Linux distro after all).
--
---------------------------------------------------------------------=
---
Post by Emmanuel Florac
Emmanuel Florac | Direction technique
| Intellique
| +33 1 78 94 84 02
---------------------------------------------------------------------=
---
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Emmanuel Florac
2014-03-03 17:35:31 UTC
Permalink
Le Mon, 3 Mar 2014 16:57:44 +0000
Post by Istvan Hubay Cebrian
So I do have ESXi on one of the blade servers. Curiously "lspci -nn"
output is very different. I for example don't see two RAID controller=
s
Post by Istvan Hubay Cebrian
=20
...
00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic
53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
...
Strange, do you access the shared storage in this case? Because it
doesn't look at all like the same hardware (different PCI ids, to begin
with).

--=20
-----------------------------------------------------------------------=
-
Emmanuel Florac | Direction technique
| Intellique
| <***@intellique.com>
| +33 1 78 94 84 02
-----------------------------------------------------------------------=
-
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Istvan Hubay Cebrian
2014-03-03 17:56:04 UTC
Permalink
You are absolutely correct. I was on the wrong machine entirely. Sorry
(this is what lack of sleep causes). So here is what I could get from
the ESXi machine:

--

00:00:1f.2 SATA controller Mass storage controller: Intel Corporation
Patsburg 6 Port SATA AHCI Controller [vmhba0]
Class 0106: 8086:1d02

00:01:00.0 RAID bus controller Mass storage controller: LSI Logic /
Symbios Logic MegaRAID SAS SKINNY Controller [vmhba1]
Class 0104: 1000:0073

00:08:00.0 RAID bus controller Mass storage controller: LSI Logic /
Symbios Logic Shared PERC 8 Mini [vmhba2]
Class 0104: 1000:002f

--

~ # esxcli system module list
Name Is Loaded Is Enabled
----------------------------- --------- ----------
vmkernel true true
chardevs true true
user true true
procfs true true
vfat true true
vmkapi_socket true true
vmkapi_v2_0_0_0_vmkernel_shim true true
vmkplexer true true
vmklinux_9 true true
vmklinux_9_2_0_0 true true
vmklinux_9_2_1_0 true true
random true true
usb true true
ehci-hcd true true
hid true true
ipmi_msghandler true true
ipmi_si_drv true true
ipmi_devintf true true
procMisc true true
iscsi_trans true true
etherswitch true true
netsched true true
cnic_register true true
tg3 true true
vmkapi_v2_0_0_0_iscsi_shim true true
vmci true true
dell true true
vmkapei true true
healthchk true true
teamcheck true true
vlanmtucheck true true
heartbeat true true
shaper true true
lldp true true
cdp true true
ipfix true true
tcpip3 true true
dvsdev true true
vdl2 true true
dvfilter true true
lacp true true
vmkapi_v2_0_0_0_dvfilter_shim true true
dvfilter-generic-fastpath true true
vmkstatelogger true true
svmmirror true true
cbt true true
migrate true true
esxfw true true
dm true true
nmp true true
vmw_satp_local true true
vmw_satp_default_aa true true
vmw_psp_lib true true
vmw_psp_fixed true true
vmw_psp_rr true true
vmw_psp_mru true true
libata_92 true true
libata_9_2_0_0 true true
usb-storage true true
vmkapi_v2_0_0_0_nmp_shim true true
hbr_filter true true
libfc_92 true true
libfcoe_92 true true
libfc_9_2_0_0 true true
libfcoe_9_2_0_0 true true
ahci true true
megaraid_sas true true
cnic true true
bnx2fc true true
lvmdriver true true
deltadisk true true
sunrpc true true
nfsclient true true
vprobe true true
vmkibft true true
vmfs3 true true

~ # esxcli system module get -m megaraid_sas
Module: megaraid_sas
Module File: /usr/lib/vmware/vmkmod/megaraid_sas
License: GPL
Version: Version 06.801.52.00, Build: 472560, Interface: 9.2 Built
on: Feb 7 2013
Signed Status: Unsigned
Signature Issuer:
Signature Digest: 50bd fb02 0df9 4ad0 3d99 00de 9234 f055 f7d2 f81e
aadf 7120 a941 44b3 61a6 d3b1
Signature FingerPrint: 0000 0000 0000 0000 0000 0000 0000 0000
Provided Namespaces:
Required Namespaces: ***@9.2.0.0, com.vmware.vmkapi=
@v2_0_0_0
--
Istvan Hubay Cebrian
http://icebrian.net
Post by Emmanuel Florac
Le Mon, 3 Mar 2014 16:57:44 +0000
Post by Istvan Hubay Cebrian
So I do have ESXi on one of the blade servers. Curiously "lspci -nn"
output is very different. I for example don't see two RAID controlle=
rs
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
...
00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic
53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
...
Strange, do you access the shared storage in this case? Because it
doesn't look at all like the same hardware (different PCI ids, to beg=
in
Post by Emmanuel Florac
with).
--
---------------------------------------------------------------------=
---
Post by Emmanuel Florac
Emmanuel Florac | Direction technique
| Intellique
| +33 1 78 94 84 02
---------------------------------------------------------------------=
---
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Emmanuel Florac
2014-03-03 18:05:35 UTC
Permalink
Le Mon, 3 Mar 2014 17:56:04 +0000
Post by Istvan Hubay Cebrian
~ # esxcli system module get -m megaraid_sas
Module: megaraid_sas
Module File: /usr/lib/vmware/vmkmod/megaraid_sas
License: GPL
Version: Version 06.801.52.00, Build: 472560, Interface: 9.2 Built
on: Feb 7 2013
Signed Status: Unsigned
Signature Digest: 50bd fb02 0df9 4ad0 3d99 00de 9234 f055 f7d2 f81=
e
Post by Istvan Hubay Cebrian
aadf 7120 a941 44b3 61a6 d3b1
Signature FingerPrint: 0000 0000 0000 0000 0000 0000 0000 0000
OK so this looks like the normal megaraid_sas under the usual license,
though it obviously works with the weird device:


00:08:00.0 RAID bus controller Mass storage controller: LSI Logic /
Symbios Logic Shared PERC 8 Mini [vmhba2]
Class 0104: 1000:002f

Could you grab the file /usr/lib/vmware/vmkmod/megaraid_sas.ko and run
modinfo on it (even from a different distro, should work fine I
suppose).

--=20
-----------------------------------------------------------------------=
-
Emmanuel Florac | Direction technique
| Intellique
| <***@intellique.com>
| +33 1 78 94 84 02
-----------------------------------------------------------------------=
-
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Istvan Hubay Cebrian
2014-03-03 18:14:37 UTC
Permalink
Here you go (ran modinfo on my Fedora machine):

[***@laptop megaraid]$ modinfo megaraid_sas
filename:
/lib/modules/3.13.5-200.fc20.x86_64/kernel/drivers/scsi/megaraid/megara=
id_sas.ko
description: LSI MegaRAID SAS Driver
author: ***@lsi.com
version: 06.700.06.00-rc1
license: GPL
srcversion: CC8C2EAD4EB0EC0F8B7526C
alias: pci:v00001000d0000005Fsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Dsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Bsv*sd*bc*sc*i*
alias: pci:v00001028d00000015sv*sd*bc*sc*i*
alias: pci:v00001000d00000413sv*sd*bc*sc*i*
alias: pci:v00001000d00000071sv*sd*bc*sc*i*
alias: pci:v00001000d00000073sv*sd*bc*sc*i*
alias: pci:v00001000d00000079sv*sd*bc*sc*i*
alias: pci:v00001000d00000078sv*sd*bc*sc*i*
alias: pci:v00001000d0000007Csv*sd*bc*sc*i*
alias: pci:v00001000d00000060sv*sd*bc*sc*i*
alias: pci:v00001000d00000411sv*sd*bc*sc*i*
depends:
intree: Y
vermagic: 3.13.5-200.fc20.x86_64 SMP mod_unload
signer: Fedora kernel signing key
sig_key: C8:CA:53:8E:94:4B:80:33:51:31:F3:2F:C0:A6:F5:54:E4:8D:A=
1:78
sig_hashalgo: sha256
parm: max_sectors:Maximum number of sectors per IO command (i=
nt)
parm: msix_disable:Disable MSI-X interrupt handling. Default:=
0 (int)
parm: msix_vectors:MSI-X max vector count. Default: Set by FW=
(int)
parm: throttlequeuedepth:Adapter queue depth when throttled
due to I/O timeout. Default: 16 (int)
parm: resetwaittime:Wait time in seconds after I/O timeout
before resetting adapter. Default: 180 (int)
--
Istvan Hubay Cebrian
http://icebrian.net
Post by Emmanuel Florac
Le Mon, 3 Mar 2014 17:56:04 +0000
Post by Istvan Hubay Cebrian
~ # esxcli system module get -m megaraid_sas
Module: megaraid_sas
Module File: /usr/lib/vmware/vmkmod/megaraid_sas
License: GPL
Version: Version 06.801.52.00, Build: 472560, Interface: 9.2 Buil=
t
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
on: Feb 7 2013
Signed Status: Unsigned
Signature Digest: 50bd fb02 0df9 4ad0 3d99 00de 9234 f055 f7d2 f8=
1e
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
aadf 7120 a941 44b3 61a6 d3b1
Signature FingerPrint: 0000 0000 0000 0000 0000 0000 0000 0000
OK so this looks like the normal megaraid_sas under the usual license=
,
Post by Emmanuel Florac
00:08:00.0 RAID bus controller Mass storage controller: LSI Logic /
Symbios Logic Shared PERC 8 Mini [vmhba2]
Class 0104: 1000:002f
Could you grab the file /usr/lib/vmware/vmkmod/megaraid_sas.ko and ru=
n
Post by Emmanuel Florac
modinfo on it (even from a different distro, should work fine I
suppose).
--
---------------------------------------------------------------------=
---
Post by Emmanuel Florac
Emmanuel Florac | Direction technique
| Intellique
| +33 1 78 94 84 02
---------------------------------------------------------------------=
---
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Istvan Hubay Cebrian
2014-03-03 18:26:31 UTC
Permalink
Sorry. I just realized this is not what you wanted. That was for my
own megaraid module on my own machine. There aparently is no
megaraid_sas.ko file in the ESXi machine only a "megaraid_sas" which I
can't seem to use modinfo on.
--
Istvan Hubay Cebrian
http://icebrian.net
/lib/modules/3.13.5-200.fc20.x86_64/kernel/drivers/scsi/megaraid/mega=
raid_sas.ko
description: LSI MegaRAID SAS Driver
version: 06.700.06.00-rc1
license: GPL
srcversion: CC8C2EAD4EB0EC0F8B7526C
alias: pci:v00001000d0000005Fsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Dsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Bsv*sd*bc*sc*i*
alias: pci:v00001028d00000015sv*sd*bc*sc*i*
alias: pci:v00001000d00000413sv*sd*bc*sc*i*
alias: pci:v00001000d00000071sv*sd*bc*sc*i*
alias: pci:v00001000d00000073sv*sd*bc*sc*i*
alias: pci:v00001000d00000079sv*sd*bc*sc*i*
alias: pci:v00001000d00000078sv*sd*bc*sc*i*
alias: pci:v00001000d0000007Csv*sd*bc*sc*i*
alias: pci:v00001000d00000060sv*sd*bc*sc*i*
alias: pci:v00001000d00000411sv*sd*bc*sc*i*
intree: Y
vermagic: 3.13.5-200.fc20.x86_64 SMP mod_unload
signer: Fedora kernel signing key
sig_key: C8:CA:53:8E:94:4B:80:33:51:31:F3:2F:C0:A6:F5:54:E4:8D=
:A1:78
sig_hashalgo: sha256
parm: max_sectors:Maximum number of sectors per IO command =
(int)
parm: msix_disable:Disable MSI-X interrupt handling. Defaul=
t: 0 (int)
parm: msix_vectors:MSI-X max vector count. Default: Set by =
=46W (int)
parm: throttlequeuedepth:Adapter queue depth when throttled
due to I/O timeout. Default: 16 (int)
parm: resetwaittime:Wait time in seconds after I/O timeout
before resetting adapter. Default: 180 (int)
--
Istvan Hubay Cebrian
http://icebrian.net
Post by Emmanuel Florac
Le Mon, 3 Mar 2014 17:56:04 +0000
Post by Istvan Hubay Cebrian
~ # esxcli system module get -m megaraid_sas
Module: megaraid_sas
Module File: /usr/lib/vmware/vmkmod/megaraid_sas
License: GPL
Version: Version 06.801.52.00, Build: 472560, Interface: 9.2 Bui=
lt
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
on: Feb 7 2013
Signed Status: Unsigned
Signature Digest: 50bd fb02 0df9 4ad0 3d99 00de 9234 f055 f7d2 f=
81e
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
aadf 7120 a941 44b3 61a6 d3b1
Signature FingerPrint: 0000 0000 0000 0000 0000 0000 0000 0000
OK so this looks like the normal megaraid_sas under the usual licens=
e,
Post by Emmanuel Florac
00:08:00.0 RAID bus controller Mass storage controller: LSI Logic /
Symbios Logic Shared PERC 8 Mini [vmhba2]
Class 0104: 1000:002f
Could you grab the file /usr/lib/vmware/vmkmod/megaraid_sas.ko and r=
un
Post by Emmanuel Florac
modinfo on it (even from a different distro, should work fine I
suppose).
--
--------------------------------------------------------------------=
----
Post by Emmanuel Florac
Emmanuel Florac | Direction technique
| Intellique
| +33 1 78 94 84 02
--------------------------------------------------------------------=
----
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Istvan Hubay Cebrian
2014-03-03 18:44:50 UTC
Permalink
Btw one other thing, but how can we be sure its the megaraid_sas
module being used to provide support for the
Post by Istvan Hubay Cebrian
00:08:00.0 RAID bus controller Mass storage controller: LSI Logic /
Symbios Logic Shared PERC 8 Mini [vmhba2]
Class 0104: 1000:002f
00:01:00.0 RAID bus controller Mass storage controller: LSI Logic /
Symbios Logic MegaRAID SAS SKINNY Controller [vmhba1]
Class 0104: 1000:0073
Specifically stated "MegaRAID" whilst the Shared PERC 8 does not. In
the module listing I can't clearly identify any module that would be
responsible for providing support to the shared PERC 8 controller so I
am not sure if sending you this
Post by Istvan Hubay Cebrian
~ # esxcli system module get -m megaraid_sas
Module: megaraid_sas
Module File: /usr/lib/vmware/vmkmod/megaraid_sas
License: GPL
Version: Version 06.801.52.00, Build: 472560, Interface: 9.2 Built
on: Feb 7 2013
Signed Status: Unsigned
Signature Digest: 50bd fb02 0df9 4ad0 3d99 00de 9234 f055 f7d2 f81=
e
Post by Istvan Hubay Cebrian
aadf 7120 a941 44b3 61a6 d3b1
Signature FingerPrint: 0000 0000 0000 0000 0000 0000 0000 0000
Was in fact correct or not.
Post by Istvan Hubay Cebrian
Sorry. I just realized this is not what you wanted. That was for my
own megaraid module on my own machine. There aparently is no
megaraid_sas.ko file in the ESXi machine only a "megaraid_sas" which =
I
Post by Istvan Hubay Cebrian
can't seem to use modinfo on.
--
Istvan Hubay Cebrian
http://icebrian.net
/lib/modules/3.13.5-200.fc20.x86_64/kernel/drivers/scsi/megaraid/meg=
araid_sas.ko
Post by Istvan Hubay Cebrian
description: LSI MegaRAID SAS Driver
version: 06.700.06.00-rc1
license: GPL
srcversion: CC8C2EAD4EB0EC0F8B7526C
alias: pci:v00001000d0000005Fsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Dsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Bsv*sd*bc*sc*i*
alias: pci:v00001028d00000015sv*sd*bc*sc*i*
alias: pci:v00001000d00000413sv*sd*bc*sc*i*
alias: pci:v00001000d00000071sv*sd*bc*sc*i*
alias: pci:v00001000d00000073sv*sd*bc*sc*i*
alias: pci:v00001000d00000079sv*sd*bc*sc*i*
alias: pci:v00001000d00000078sv*sd*bc*sc*i*
alias: pci:v00001000d0000007Csv*sd*bc*sc*i*
alias: pci:v00001000d00000060sv*sd*bc*sc*i*
alias: pci:v00001000d00000411sv*sd*bc*sc*i*
intree: Y
vermagic: 3.13.5-200.fc20.x86_64 SMP mod_unload
signer: Fedora kernel signing key
sig_key: C8:CA:53:8E:94:4B:80:33:51:31:F3:2F:C0:A6:F5:54:E4:8=
D:A1:78
Post by Istvan Hubay Cebrian
sig_hashalgo: sha256
parm: max_sectors:Maximum number of sectors per IO command=
(int)
Post by Istvan Hubay Cebrian
parm: msix_disable:Disable MSI-X interrupt handling. Defau=
lt: 0 (int)
Post by Istvan Hubay Cebrian
parm: msix_vectors:MSI-X max vector count. Default: Set by=
FW (int)
Post by Istvan Hubay Cebrian
parm: throttlequeuedepth:Adapter queue depth when throttle=
d
Post by Istvan Hubay Cebrian
due to I/O timeout. Default: 16 (int)
parm: resetwaittime:Wait time in seconds after I/O timeout
before resetting adapter. Default: 180 (int)
--
Istvan Hubay Cebrian
http://icebrian.net
Post by Emmanuel Florac
Le Mon, 3 Mar 2014 17:56:04 +0000
Post by Istvan Hubay Cebrian
~ # esxcli system module get -m megaraid_sas
Module: megaraid_sas
Module File: /usr/lib/vmware/vmkmod/megaraid_sas
License: GPL
Version: Version 06.801.52.00, Build: 472560, Interface: 9.2 Bu=
ilt
Post by Istvan Hubay Cebrian
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
on: Feb 7 2013
Signed Status: Unsigned
Signature Digest: 50bd fb02 0df9 4ad0 3d99 00de 9234 f055 f7d2 =
f81e
Post by Istvan Hubay Cebrian
Post by Emmanuel Florac
Post by Istvan Hubay Cebrian
aadf 7120 a941 44b3 61a6 d3b1
Signature FingerPrint: 0000 0000 0000 0000 0000 0000 0000 0000
OK so this looks like the normal megaraid_sas under the usual licen=
se,
Post by Istvan Hubay Cebrian
Post by Emmanuel Florac
00:08:00.0 RAID bus controller Mass storage controller: LSI Logic /
Symbios Logic Shared PERC 8 Mini [vmhba2]
Class 0104: 1000:002f
Could you grab the file /usr/lib/vmware/vmkmod/megaraid_sas.ko and =
run
Post by Istvan Hubay Cebrian
Post by Emmanuel Florac
modinfo on it (even from a different distro, should work fine I
suppose).
--
-------------------------------------------------------------------=
-----
Post by Istvan Hubay Cebrian
Post by Emmanuel Florac
Emmanuel Florac | Direction technique
| Intellique
| +33 1 78 94 84 02
-------------------------------------------------------------------=
-----
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Emmanuel Florac
2014-03-03 20:37:12 UTC
Permalink
Post by Istvan Hubay Cebrian
Specifically stated "MegaRAID" whilst the Shared PERC 8 does not. In
the module listing I can't clearly identify any module that would be
responsible for providing support to the shared PERC 8 controller
Well I went through the module list and couldn't find anything else
that could reasonably fit with an LSI driver, so I'm pretty sure it
must be the megaraid driver... If only it could be a normal Linux
system, alas.

--=20
-----------------------------------------------------------------------=
-
Emmanuel Florac | Direction technique
| Intellique
| <***@intellique.com>
| +33 1 78 94 84 02
-----------------------------------------------------------------------=
-
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" i=
n
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
adam radford
2014-03-03 21:01:40 UTC
Permalink
Istvan/Emmanuel,
Post by Istvan Hubay Cebrian
08:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID
SAS 2208 IOV [Thunderbolt] [1000:002f] (rev 05)

I will be sending a driver patch for megaraid_sas to support the Dell
PowerEdge VRTX/Shared PERC8 device later this week. This will allow
you to run Linux with the megaraid_sas in Virtual Function (VF) mode
on the VRTX blades.

-Adam
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Istvan Hubay Cebrian
2014-03-03 21:14:02 UTC
Permalink
Post by adam radford
I will be sending a driver patch for megaraid_sas to support the Dell
PowerEdge VRTX/Shared PERC8 device later this week. This will allow
you to run Linux with the megaraid_sas in Virtual Function (VF) mode
on the VRTX blades.
That is great news Adam! Many thanks for that. Might I just ask, was
this something you where already working on or something more recent?

Also, if its not too much trouble I would like to understand how
support is typically added/considered, does LSI have to provide you
with info, is the community responsible for knowing what new hardware
is out and when possible support it, does Dell/LSI (anyone) provide
any support in this respect? (just trying to understand if me coming
to this mailing list was at all necessary or useful)

In any case, this is definitely great and very welcomed news. Looking
forward to hearing from you some more.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Loading...