Re: [Scst-devel] SRPT - mlx4_0 Drive not found

[<Ad...@Do...>]

Thanks to everyone to point me in the right direction on this. However I am
facing another issue related to this.

To enable the option I use the following cmd:

modprobe ib_srpt use_node_guid_in_target_name

I added this to /etc/modules file to load at startup, however it doesn't
appear to be working.

After startup I have to rmmod ib_srpt and then run the modprobe able and
then it seems to take and start working.

How can I get the use_node_guid_in_target_name to load on startup properly?

Thanks,

Jonathan 

-----Original Message-----
From: Curtis [mailto:cu...@ti...] 
Sent: Wednesday, October 19, 2011 9:24 PM
To: Ad...@Do...
Cc: scs...@li...; bar...@gm...
Subject: Re: [Scst-devel] SRPT - mlx4_0 Drive not found

On 20/10/11 10:58, Ad...@Do... wrote:
> I have enabled this target:
>
> Dmesg outputed:
>
> scst: Using autogenerated rel ID 1 for target ib_srpt_target_0
>
> However, the mlx4_0 driver doesn't even appear as a target. All there 
> is is
> this:
>
> netmanvm1:~# cat
> /sys/kernel/scst_tgt/targets/ib_srpt/ib_srpt_target_0/enabled
> 1

> I have tried to enable it as a target with the IB adapter GUID but it 
> still is giving the exact same error.

In the dmesg dump you gave before, you'll see:

ib_srpt: ***WARNING***: Usage of HCA numbers as SCST target names is
deprecated and will be removed in one of the next versions. It is strongly
recommended to set use_node_guid_in_target_name parameter in 1 and update
your SCST config file accordingly to use HCAs GUIDs.

This means that the srpt driver will create "ib_srpt_target_N" for each HCA
in your system.

So, what you're seeing as "ib_srpt_target_0" is the target bound to the
first IB HCA in your system.  It will NOT show up as "mlx4_0" or anything
related to the kernel driver for the IB device.

If you set "use_node_guid_in_target_name", it will do as it says, and use
the GUID instead of the generated name.

> How to I enabled mlx4_0 when it is not appearing as an ib_srpt target?

It _is_ appearing, just not with the name you're expecting.

> When I reboot the server the ib_srpt_target_0 is disabled again. I 
> guess this will be fixed once this driver issue is sorted.

You have to enable it on each boot.  It's generally best to configure your
LUNs and Groups _before_ enabling the target, to avoid giving unmasked
access to LUNs [albeit for a short time].

Typically, you'd use /etc/scst.conf to retail your desired config, and have
it loaded on boot.

--
Curtis