topic linux sudden misbehaviour with MSA2000 fc in HPE EVA Storage

linux sudden misbehaviour with MSA2000 fc

Nima Gh. — Wed, 09 Jun 2010 13:30:19 GMT

The device was working well and windows was detecting the luns asd /dev/sdX devices, but when I removed all (unformatted) vdisks and recreated another vdisks and volumes, linux fails detecting the devices and shows them as non-block sgX devices! What is wrong with that?

Re: linux sudden misbehaviour with MSA2000 fc

Uwe Zessin — Wed, 09 Jun 2010 14:18:44 GMT

"sg" devices represent so-called "controller LUNs". Those are special SCSI communication LUNs which do not provide storage. I'm pretty sure Linux has seen them before, because the MSA presents a controller device at LUN address #0 on each controller host port.

It sounds like you have created vdisk(s) and volumes, but did not present the volumes to the host(s).

Re: linux sudden misbehaviour with MSA2000 fc

Nima Gh. — Sat, 12 Jun 2010 06:44:31 GMT

Thanks for your reply! Do I need to do some extra work? How should I Present the Volumes to hosts? I thought that identifying hosts by MSA2000 is enough!
I remember, Hosts HBA card can detect MSA2000 device! and MSA2000 can see the hosts! but devices are not created successfully!

Re: linux sudden misbehaviour with MSA2000 fc

Nima Gh. — Sun, 13 Jun 2010 09:44:58 GMT

Thanks! I performed mapping and the problem is solved now!