Skip to contentSkip to conversation

: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

ANNOUNCE Vladislav Bolkhovitin 4 participants 13 messages Apr 14, 2009 – Jun 12, 2009 SCSI

lore
Share & tools
lore

Vladislav Bolkhovitin

author
#0 lore raw

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards has been just added in the SCST SVN repository. A lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell 88SE64xx or 88SE94xx chips as a SAN storage server (target). More info you can find on the SCST page http://scst.sourceforge.net.

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Vlad

#1 lore raw
Quoted 9 lines · Vladislav Bolkhovitin

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards has been just added in the SCST SVN repository. A lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell 88SE64xx or 88SE94xx chips as a SAN storage server (target). More info you can find on the SCST page http://scst.sourceforge.net.

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Nice!

I'm glad to see this progressing. I'm amazed that some of my original mvsas code still remains :)

I'll give this a shot on my 6440.

Jeff

#2 lore raw
In reply to Vladislav Bolkhovitin
Quoted 4 lines

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards has been just added in the SCST SVN repository.

A

Quoted 3 lines

lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell 88SE64xx

or

Quoted 1 line

88SE94xx chips as a SAN storage server (target). More info you can

find

Quoted 6 lines

on the SCST page http://scst.sourceforge.net.

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Hi Vlad/Andy,

Is this target driver expected to work with 6320 cards as well? Using this driver, I was able to discover a SATA drive connected to the 6320 in initiator mode.

I connected the 6320 directly to a second 6320 on another machine, set up a virtual LUN with SCST (added to the default group, etc.) and enabled target mode, but I'm not seeing anything on the initiator side.

Brian

#3 lore raw

Brian,
This driver can work with 6320, and I will add a README for this target driver with next updates for code, I think you will find the cause you can't detect the LUN.

Regards
Andy Yan

-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: 2009年6月6日 2:10
To: [email protected]; [email protected]
Cc: [email protected]; Andy Yan; [email protected]
Subject: RE: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 4 lines

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards has been just added in the SCST SVN repository.

A

Quoted 3 lines

lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell 88SE64xx

or

Quoted 1 line

88SE94xx chips as a SAN storage server (target). More info you can

find

Quoted 6 lines

on the SCST page http://scst.sourceforge.net.

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Hi Vlad/Andy,

Is this target driver expected to work with 6320 cards as well? Using this driver, I was able to discover a SATA drive connected to the 6320 in initiator mode.

I connected the 6320 directly to a second 6320 on another machine, set up a virtual LUN with SCST (added to the default group, etc.) and enabled target mode, but I'm not seeing anything on the initiator side.

Brian

author
#4 lore raw
In reply to [email protected]

Hi Brian,

Quoted 20 lines · [email protected], on 06/05/2009 10:10 PM wrote:
Quoted 4 lines

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards has been just added in the SCST SVN repository.

A

Quoted 3 lines

lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell 88SE64xx

or

Quoted 1 line

88SE94xx chips as a SAN storage server (target). More info you can

find

Quoted 6 lines

on the SCST page http://scst.sourceforge.net.

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Hi Vlad/Andy,

Quoted 7 lines

Is this target driver expected to work with 6320 cards as well? Using this driver, I was able to discover a SATA drive connected to the 6320 in initiator mode.

I connected the 6320 directly to a second 6320 on another machine, set up a virtual LUN with SCST (added to the default group, etc.) and enabled target mode, but I'm not seeing anything on the initiator side.

Double check you don't have in the kernel log messages like "tgt_dev for LUN X not found, command to unexisting LU?" (I assume you have SCST tracing enabled, it is by default so in the SVN trunk/). If you do, then you didn't setup the virtual LUN correctly.

Vlad

#5 lore raw
Quoted 6 lines
Quoted 3 lines · [email protected], on 06/05/2009 10:10 PM wrote:
Quoted 3 lines

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G)

and

Quoted 1 line
Quoted 1 line
Quoted 1 line

88SE94xx(6G) SAS cards has been just added in the SCST SVN

repository.

Quoted 4 lines
Quoted 4 lines

A

Quoted 3 lines

lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell

88SE64xx

Quoted 5 lines
Quoted 5 lines

or

Quoted 1 line

88SE94xx chips as a SAN storage server (target). More info you can

find

Quoted 2 lines

on the SCST page http://scst.sourceforge.net.

Quoted 8 lines
Quoted 8 lines
Quoted 4 lines

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Hi Vlad/Andy,

Is this target driver expected to work with 6320 cards as well?

Using

Quoted 1 line
Quoted 1 line

this driver, I was able to discover a SATA drive connected to the

6320

Quoted 3 lines
Quoted 3 lines

in initiator mode.

I connected the 6320 directly to a second 6320 on another machine,

set

Quoted 2 lines
Quoted 2 lines

up a virtual LUN with SCST (added to the default group, etc.) and enabled target mode, but I'm not seeing anything on the initiator

side.

Quoted 2 lines

Double check you don't have in the kernel log messages like "tgt_dev

for

Quoted 2 lines

LUN X not found, command to unexisting LU?" (I assume you have SCST tracing enabled, it is by default so in the SVN trunk/). If you do,

then

Quoted 3 lines

you didn't setup the virtual LUN correctly.

Vlad

Thanks Vlad. I think my SCST configuration is Ok. I did experiment previously with the iSCSI target and the scst_local driver, and both worked fine.

Andy,

Thanks for the README. I followed the steps in the file and see the same result. The following shows the commands I'm using and the associated output.

On the target side, I load the SCST/mvsas drivers and enable target mode. This looks like it works, but my 'target_mode' file is slightly different from what is shown in the README:

root@ix12-1:/sys/class/scsi_host/host17# cat target_mode
phy  dev sas address     attach dev type   attach sas address  target
mode
0    5005043011ab0000                      0                   0
1    5005043011ab0000                      0                   0
2    5005043011ab0000                      0                   0
3    5005043011ab0000                      0                   0
root@ix12-1:/sys/class/scsi_host/host17# echo "enable 1" > target_mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_init.c
898:get enable
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_init.c
853:Enable phy1
Jun  8 09:53:20 ix12-1 kernel: scst: Target mvst_scst (db0f2cc0) for
template mvst_scst registered successfully
Jun  8 09:53:20 ix12-1 kernel: [3054]: mvst_register_tgt_handler:Enable
lun for host 0(0,db140000)
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2290:initiator attaching 0000000000000000,map 2 on port[1]
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 0 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 1 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 2 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 3 to target mode
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[0] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[1] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[2] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[3] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2301:Enable target mode......
root@ix12-1:/sys/class/scsi_host/host17# cat target_mode
phy  dev sas address     attach dev type   attach sas address  target
mode
0    5005043011ab0000                      0                   1
1    5005043011ab0000                      0                   1
2    5005043011ab0000                      0                   1
3    5005043011ab0000                      0                   1

Next, I create the virtual LUN and add it to the default group as LUN 0:

root@ix12-1:/proc/scsi_tgt/vdisk# echo "open test
/mnt/soho_storage/disk" > vdisk
Jun  8 09:54:27 ix12-1 kernel: dev_vdisk: Registering virtual FILEIO
device test
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4791
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4792
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4793
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4794
Jun  8 09:54:27 ix12-1 kernel: dev_vdisk: Attached SCSI target virtual
disk test (file="/mnt/soho_storage/disk", fs=1000MB, bs=512,
nblocks=2048000, cyln=1000)
Jun  8 09:54:27 ix12-1 kernel: scst: Attached SCSI target mid-level to
virtual device test (id 1)
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4795
root@ix12-1:/proc/scsi_tgt# echo "add test" > groups/Default/devices
Jun  8 09:55:19 ix12-1 kernel: scst: Added device test to group Default
(LUN 0, rd_only 0)

... and finally, I load the mvsas driver on the initiator side:

root@ix12-2:/# modprobe mvsas
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi0, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi1, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi2, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi5, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi6, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi7, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi8, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi9, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi10, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi12, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi13, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi14, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi15, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Processing thread started, PID 9166
Jun  8 21:56:04 ix12-2 kernel: scst: Init thread started, PID 9167
Jun  8 21:56:04 ix12-2 kernel: scst: Task management thread started, PID
9168
Jun  8 21:56:04 ix12-2 kernel: scst: SCST version 1.0.1 loaded
successfully (max mem for commands 221MB, per device 88MB)
Jun  8 21:56:04 ix12-2 kernel: scst: Enabled features: TRACING
Jun  8 21:56:04 ix12-2 kernel: scst: Management thread started, PID 9169
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: mvsas: driver version
0.8.3
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: PCI INT A ->
Link[LNKA] -> GSI 5 (level, low) -> IRQ 5
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: setting latency timer
to 64
Jun  8 21:56:05 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
491:Init flash rom ok,flash type is 0x101.
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 0 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 1 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 2 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 3 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: mvsas 0000:03:00.0: mvsas: PCI-E x1,
Bandwidth Usage: 2.5 Gbps
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 0 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 0 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 1 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 1 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 2 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 2 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 3 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 3 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: scsi17 : mvsas
Jun  8 21:56:08 ix12-2 kernel: scst: Target template mvst_scst
registered successfully

At this point I would have expected a new SCSI disk to appear for the virtual LUN, any thoughts? Thanks.

Brian

#6 lore raw

Brian,
Please set unique SAS address for each SAS port of target controller, and make sure you do correct connection, you can get the SAS address of attaching device from "attach sas address ".Then enable target mode and add target LUN.

Regards
Andy Yan

-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: 2009年6月9日 2:14
To: [email protected]
Cc: [email protected]; [email protected]; Andy Yan; [email protected]
Subject: RE: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 4 lines
Quoted 3 lines · [email protected], on 06/05/2009 10:10 PM wrote:
Quoted 3 lines

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G)

and

Quoted 1 line
Quoted 1 line
Quoted 1 line

88SE94xx(6G) SAS cards has been just added in the SCST SVN

repository.

Quoted 4 lines
Quoted 4 lines

A

Quoted 3 lines

lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell

88SE64xx

Quoted 5 lines
Quoted 5 lines

or

Quoted 1 line

88SE94xx chips as a SAN storage server (target). More info you can

find

Quoted 2 lines

on the SCST page http://scst.sourceforge.net.

Quoted 8 lines
Quoted 8 lines
Quoted 4 lines

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Hi Vlad/Andy,

Is this target driver expected to work with 6320 cards as well?

Using

Quoted 1 line
Quoted 1 line

this driver, I was able to discover a SATA drive connected to the

6320

Quoted 3 lines
Quoted 3 lines

in initiator mode.

I connected the 6320 directly to a second 6320 on another machine,

set

Quoted 2 lines
Quoted 2 lines

up a virtual LUN with SCST (added to the default group, etc.) and enabled target mode, but I'm not seeing anything on the initiator

side.

Quoted 2 lines

Double check you don't have in the kernel log messages like "tgt_dev

for

Quoted 2 lines

LUN X not found, command to unexisting LU?" (I assume you have SCST tracing enabled, it is by default so in the SVN trunk/). If you do,

then

Quoted 3 lines

you didn't setup the virtual LUN correctly.

Vlad

Thanks Vlad. I think my SCST configuration is Ok. I did experiment previously with the iSCSI target and the scst_local driver, and both worked fine.

Andy,

Thanks for the README. I followed the steps in the file and see the same result. The following shows the commands I'm using and the associated output.

On the target side, I load the SCST/mvsas drivers and enable target mode. This looks like it works, but my 'target_mode' file is slightly different from what is shown in the README:

root@ix12-1:/sys/class/scsi_host/host17# cat target_mode
phy  dev sas address     attach dev type   attach sas address  target
mode
0    5005043011ab0000                      0                   0
1    5005043011ab0000                      0                   0
2    5005043011ab0000                      0                   0
3    5005043011ab0000                      0                   0
root@ix12-1:/sys/class/scsi_host/host17# echo "enable 1" > target_mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_init.c
898:get enable
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_init.c
853:Enable phy1
Jun  8 09:53:20 ix12-1 kernel: scst: Target mvst_scst (db0f2cc0) for
template mvst_scst registered successfully
Jun  8 09:53:20 ix12-1 kernel: [3054]: mvst_register_tgt_handler:Enable
lun for host 0(0,db140000)
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2290:initiator attaching 0000000000000000,map 2 on port[1]
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 0 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 1 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 2 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 3 to target mode
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[0] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[1] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[2] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[3] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2301:Enable target mode......
root@ix12-1:/sys/class/scsi_host/host17# cat target_mode
phy  dev sas address     attach dev type   attach sas address  target
mode
0    5005043011ab0000                      0                   1
1    5005043011ab0000                      0                   1
2    5005043011ab0000                      0                   1
3    5005043011ab0000                      0                   1

Next, I create the virtual LUN and add it to the default group as LUN 0:

root@ix12-1:/proc/scsi_tgt/vdisk# echo "open test
/mnt/soho_storage/disk" > vdisk
Jun  8 09:54:27 ix12-1 kernel: dev_vdisk: Registering virtual FILEIO
device test
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4791
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4792
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4793
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4794
Jun  8 09:54:27 ix12-1 kernel: dev_vdisk: Attached SCSI target virtual
disk test (file="/mnt/soho_storage/disk", fs=1000MB, bs=512,
nblocks=2048000, cyln=1000)
Jun  8 09:54:27 ix12-1 kernel: scst: Attached SCSI target mid-level to
virtual device test (id 1)
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4795
root@ix12-1:/proc/scsi_tgt# echo "add test" > groups/Default/devices
Jun  8 09:55:19 ix12-1 kernel: scst: Added device test to group Default
(LUN 0, rd_only 0)

... and finally, I load the mvsas driver on the initiator side:

root@ix12-2:/# modprobe mvsas
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi0, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi1, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi2, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi5, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi6, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi7, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi8, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi9, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi10, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi12, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi13, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi14, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi15, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Processing thread started, PID 9166
Jun  8 21:56:04 ix12-2 kernel: scst: Init thread started, PID 9167
Jun  8 21:56:04 ix12-2 kernel: scst: Task management thread started, PID
9168
Jun  8 21:56:04 ix12-2 kernel: scst: SCST version 1.0.1 loaded
successfully (max mem for commands 221MB, per device 88MB)
Jun  8 21:56:04 ix12-2 kernel: scst: Enabled features: TRACING
Jun  8 21:56:04 ix12-2 kernel: scst: Management thread started, PID 9169
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: mvsas: driver version
0.8.3
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: PCI INT A ->
Link[LNKA] -> GSI 5 (level, low) -> IRQ 5
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: setting latency timer
to 64
Jun  8 21:56:05 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
491:Init flash rom ok,flash type is 0x101.
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 0 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 1 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 2 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 3 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: mvsas 0000:03:00.0: mvsas: PCI-E x1,
Bandwidth Usage: 2.5 Gbps
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 0 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 0 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 1 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 1 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 2 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 2 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 3 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 3 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: scsi17 : mvsas
Jun  8 21:56:08 ix12-2 kernel: scst: Target template mvst_scst
registered successfully

At this point I would have expected a new SCSI disk to appear for the virtual LUN, any thoughts? Thanks.

Brian

#7 lore raw
Quoted 3 lines

Brian,
Please set unique SAS address for each SAS port of target
controller, and make sure you do correct connection, you can get the

SAS

Quoted 1 line

address of attaching device from "attach sas address ".Then enable

target

Quoted 5 lines

mode and add target LUN.

Regards
Andy Yan

Not quite sure I follow... Is this value read from HW at init time? Do we have an interface available where I can explicitly set a SAS address for the port? Thanks.

Brian

#8 lore raw

Brian,
You should get a tool for HBA parameter configuration, or you can directly change the code of setting SAS address in last function of mv_spi.c.

Regards
Andy Yan

-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: 2009年6月9日 21:03
To: Andy Yan; [email protected]
Cc: [email protected]; [email protected]; [email protected]
Subject: RE: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 3 lines

Brian,
Please set unique SAS address for each SAS port of target
controller, and make sure you do correct connection, you can get the

SAS

Quoted 1 line

address of attaching device from "attach sas address ".Then enable

target

Quoted 5 lines

mode and add target LUN.

Regards
Andy Yan

Not quite sure I follow... Is this value read from HW at init time? Do we have an interface available where I can explicitly set a SAS address for the port? Thanks.

Brian

author
#9 lore raw
In reply to Andy Yan
Quoted 5 lines · Andy Yan, on 06/09/2009 05:27 AM wrote:

Brian,
Please set unique SAS address for each SAS port of target controller, and make sure you do correct connection, you can get the SAS address of attaching device from "attach sas address ".Then enable target mode and add target LUN.

Do you mean "add target LUN and then enable target mode"? Otherwise an initiator can connect while there are no LUNs configured on the target and confused by it.

Quoted 210 lines

Regards
Andy Yan

-----Original Message-----
From: [email protected] [mailto:[email protected]] Sent: 2009年6月9日 2:14
To: [email protected]
Cc: [email protected]; [email protected]; Andy Yan; [email protected]
Subject: RE: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 4 lines
Quoted 3 lines · [email protected], on 06/05/2009 10:10 PM wrote:
Quoted 3 lines

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G)

and

Quoted 1 line
Quoted 1 line
Quoted 1 line

88SE94xx(6G) SAS cards has been just added in the SCST SVN

repository.

Quoted 4 lines
Quoted 4 lines

A

Quoted 3 lines

lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell

88SE64xx

Quoted 5 lines
Quoted 5 lines

or

Quoted 1 line

88SE94xx chips as a SAN storage server (target). More info you can

find

Quoted 2 lines

on the SCST page http://scst.sourceforge.net.

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Hi Vlad/Andy,

Is this target driver expected to work with 6320 cards as well?

Using

Quoted 1 line
Quoted 1 line

this driver, I was able to discover a SATA drive connected to the

6320

Quoted 3 lines
Quoted 3 lines

in initiator mode.

I connected the 6320 directly to a second 6320 on another machine,

set

Quoted 2 lines
Quoted 2 lines

up a virtual LUN with SCST (added to the default group, etc.) and enabled target mode, but I'm not seeing anything on the initiator

side.

Quoted 1 line

Double check you don't have in the kernel log messages like "tgt_dev

for

Quoted 2 lines

LUN X not found, command to unexisting LU?" (I assume you have SCST tracing enabled, it is by default so in the SVN trunk/). If you do,

then

Quoted 3 lines

you didn't setup the virtual LUN correctly.

Vlad

Thanks Vlad. I think my SCST configuration is Ok. I did experiment previously with the iSCSI target and the scst_local driver, and both worked fine.

Andy,

Thanks for the README. I followed the steps in the file and see the same result. The following shows the commands I'm using and the associated output.

On the target side, I load the SCST/mvsas drivers and enable target mode. This looks like it works, but my 'target_mode' file is slightly different from what is shown in the README:

root@ix12-1:/sys/class/scsi_host/host17# cat target_mode
phy  dev sas address     attach dev type   attach sas address  target
mode
0    5005043011ab0000                      0                   0
1    5005043011ab0000                      0                   0
2    5005043011ab0000                      0                   0
3    5005043011ab0000                      0                   0
root@ix12-1:/sys/class/scsi_host/host17# echo "enable 1" > target_mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_init.c
898:get enable
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_init.c
853:Enable phy1
Jun  8 09:53:20 ix12-1 kernel: scst: Target mvst_scst (db0f2cc0) for
template mvst_scst registered successfully
Jun  8 09:53:20 ix12-1 kernel: [3054]: mvst_register_tgt_handler:Enable
lun for host 0(0,db140000)
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2290:initiator attaching 0000000000000000,map 2 on port[1]
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 0 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 1 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 2 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 3 to target mode
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[0] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[1] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[2] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[3] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2301:Enable target mode......
root@ix12-1:/sys/class/scsi_host/host17# cat target_mode
phy  dev sas address     attach dev type   attach sas address  target
mode
0    5005043011ab0000                      0                   1
1    5005043011ab0000                      0                   1
2    5005043011ab0000                      0                   1
3    5005043011ab0000                      0                   1

Next, I create the virtual LUN and add it to the default group as LUN 0:

root@ix12-1:/proc/scsi_tgt/vdisk# echo "open test
/mnt/soho_storage/disk" > vdisk
Jun  8 09:54:27 ix12-1 kernel: dev_vdisk: Registering virtual FILEIO
device test
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4791
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4792
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4793
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4794
Jun  8 09:54:27 ix12-1 kernel: dev_vdisk: Attached SCSI target virtual
disk test (file="/mnt/soho_storage/disk", fs=1000MB, bs=512,
nblocks=2048000, cyln=1000)
Jun  8 09:54:27 ix12-1 kernel: scst: Attached SCSI target mid-level to
virtual device test (id 1)
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4795
root@ix12-1:/proc/scsi_tgt# echo "add test" > groups/Default/devices
Jun  8 09:55:19 ix12-1 kernel: scst: Added device test to group Default
(LUN 0, rd_only 0)

... and finally, I load the mvsas driver on the initiator side:

root@ix12-2:/# modprobe mvsas
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi0, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi1, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi2, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi5, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi6, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi7, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi8, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi9, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi10, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi12, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi13, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi14, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi15, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Processing thread started, PID 9166
Jun  8 21:56:04 ix12-2 kernel: scst: Init thread started, PID 9167
Jun  8 21:56:04 ix12-2 kernel: scst: Task management thread started, PID
9168
Jun  8 21:56:04 ix12-2 kernel: scst: SCST version 1.0.1 loaded
successfully (max mem for commands 221MB, per device 88MB)
Jun  8 21:56:04 ix12-2 kernel: scst: Enabled features: TRACING
Jun  8 21:56:04 ix12-2 kernel: scst: Management thread started, PID 9169
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: mvsas: driver version
0.8.3
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: PCI INT A ->
Link[LNKA] -> GSI 5 (level, low) -> IRQ 5
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: setting latency timer
to 64
Jun  8 21:56:05 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
491:Init flash rom ok,flash type is 0x101.
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 0 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 1 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 2 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 3 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: mvsas 0000:03:00.0: mvsas: PCI-E x1,
Bandwidth Usage: 2.5 Gbps
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 0 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 0 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 1 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 1 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 2 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 2 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 3 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 3 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: scsi17 : mvsas
Jun  8 21:56:08 ix12-2 kernel: scst: Target template mvst_scst
registered successfully
Quoted 5 lines

At this point I would have expected a new SCSI disk to appear for the virtual LUN, any thoughts? Thanks.

Brian
N嫥叉靣笡y氊b瞂千v豝�)藓{.n�+壏{北�"妠ay�蕠跈�,jf＂穐殝鄗�畐ア� ⒎:+v墾妛鑚豰稛��珣赙zZ+凒殠娸"濟!tml=

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#10 lore raw

No, enable target mode and then add LUN.

-----Original Message-----
From: Vladislav Bolkhovitin [mailto:[email protected]]
Sent: 2009年6月11日 2:41
To: Andy Yan
Cc: [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 5 lines · Andy Yan, on 06/09/2009 05:27 AM wrote:

Brian,
Please set unique SAS address for each SAS port of target controller, and make sure you do correct connection, you can get the SAS address of attaching device from "attach sas address ".Then enable target mode and add target LUN.

Do you mean "add target LUN and then enable target mode"? Otherwise an initiator can connect while there are no LUNs configured on the target and confused by it.

Quoted 211 lines

Regards
Andy Yan

-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: 2009年6月9日 2:14
To: [email protected]
Cc: [email protected]; [email protected]; Andy Yan; [email protected]
Subject: RE: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 4 lines
Quoted 3 lines · [email protected], on 06/05/2009 10:10 PM wrote:
Quoted 3 lines

Hi All,

I'm glad to announce that a target driver for Marvell 88SE64xx(3G)

and

Quoted 1 line
Quoted 1 line
Quoted 1 line

88SE94xx(6G) SAS cards has been just added in the SCST SVN

repository.

Quoted 4 lines
Quoted 4 lines

A

Quoted 3 lines

lot of thanks to Marvell and Andy Yan!

This driver allows to use a SAS controller based on Marvell

88SE64xx

Quoted 5 lines
Quoted 5 lines

or

Quoted 1 line

88SE94xx chips as a SAN storage server (target). More info you can

find

Quoted 2 lines

on the SCST page http://scst.sourceforge.net.

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines

You can download the driver from SCST SVN by running a command:

$ svn co https://scst.svn.sourceforge.net/svnroot/scst

Hi Vlad/Andy,

Is this target driver expected to work with 6320 cards as well?

Using

Quoted 1 line
Quoted 1 line

this driver, I was able to discover a SATA drive connected to the

6320

Quoted 3 lines
Quoted 3 lines

in initiator mode.

I connected the 6320 directly to a second 6320 on another machine,

set

Quoted 2 lines
Quoted 2 lines

up a virtual LUN with SCST (added to the default group, etc.) and enabled target mode, but I'm not seeing anything on the initiator

side.

Quoted 1 line

Double check you don't have in the kernel log messages like "tgt_dev

for

Quoted 2 lines

LUN X not found, command to unexisting LU?" (I assume you have SCST tracing enabled, it is by default so in the SVN trunk/). If you do,

then

Quoted 3 lines

you didn't setup the virtual LUN correctly.

Vlad

Thanks Vlad. I think my SCST configuration is Ok. I did experiment previously with the iSCSI target and the scst_local driver, and both worked fine.

Andy,

Thanks for the README. I followed the steps in the file and see the same result. The following shows the commands I'm using and the associated output.

On the target side, I load the SCST/mvsas drivers and enable target mode. This looks like it works, but my 'target_mode' file is slightly different from what is shown in the README:

root@ix12-1:/sys/class/scsi_host/host17# cat target_mode
phy  dev sas address     attach dev type   attach sas address  target
mode
0    5005043011ab0000                      0                   0
1    5005043011ab0000                      0                   0
2    5005043011ab0000                      0                   0
3    5005043011ab0000                      0                   0
root@ix12-1:/sys/class/scsi_host/host17# echo "enable 1" > target_mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_init.c
898:get enable
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_init.c
853:Enable phy1
Jun  8 09:53:20 ix12-1 kernel: scst: Target mvst_scst (db0f2cc0) for
template mvst_scst registered successfully
Jun  8 09:53:20 ix12-1 kernel: [3054]: mvst_register_tgt_handler:Enable
lun for host 0(0,db140000)
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2290:initiator attaching 0000000000000000,map 2 on port[1]
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 0 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 1 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 2 to target mode
Jun  8 09:53:20 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2199:set phy 3 to target mode
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[0] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[1] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[2] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
1779:Reset phy[3] to notify iniator
Jun  8 09:53:22 ix12-1 kernel: /home/brian/scst/mvsas_tgt/mv_tgt.c
2301:Enable target mode......
root@ix12-1:/sys/class/scsi_host/host17# cat target_mode
phy  dev sas address     attach dev type   attach sas address  target
mode
0    5005043011ab0000                      0                   1
1    5005043011ab0000                      0                   1
2    5005043011ab0000                      0                   1
3    5005043011ab0000                      0                   1

Next, I create the virtual LUN and add it to the default group as LUN 0:

root@ix12-1:/proc/scsi_tgt/vdisk# echo "open test
/mnt/soho_storage/disk" > vdisk
Jun  8 09:54:27 ix12-1 kernel: dev_vdisk: Registering virtual FILEIO
device test
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4791
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4792
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4793
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4794
Jun  8 09:54:27 ix12-1 kernel: dev_vdisk: Attached SCSI target virtual
disk test (file="/mnt/soho_storage/disk", fs=1000MB, bs=512,
nblocks=2048000, cyln=1000)
Jun  8 09:54:27 ix12-1 kernel: scst: Attached SCSI target mid-level to
virtual device test (id 1)
Jun  8 09:54:27 ix12-1 kernel: scst: Processing thread started, PID 4795
root@ix12-1:/proc/scsi_tgt# echo "add test" > groups/Default/devices
Jun  8 09:55:19 ix12-1 kernel: scst: Added device test to group Default
(LUN 0, rd_only 0)

... and finally, I load the mvsas driver on the initiator side:

root@ix12-2:/# modprobe mvsas
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi0, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi1, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi2, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi5, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi6, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi7, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi8, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi9, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi10, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi12, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi13, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi14, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Attached SCSI target mid-level at
scsi15, channel 0, id 0, lun 0, type 0
Jun  8 21:56:04 ix12-2 kernel: scst: Processing thread started, PID 9166
Jun  8 21:56:04 ix12-2 kernel: scst: Init thread started, PID 9167
Jun  8 21:56:04 ix12-2 kernel: scst: Task management thread started, PID
9168
Jun  8 21:56:04 ix12-2 kernel: scst: SCST version 1.0.1 loaded
successfully (max mem for commands 221MB, per device 88MB)
Jun  8 21:56:04 ix12-2 kernel: scst: Enabled features: TRACING
Jun  8 21:56:04 ix12-2 kernel: scst: Management thread started, PID 9169
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: mvsas: driver version
0.8.3
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: PCI INT A ->
Link[LNKA] -> GSI 5 (level, low) -> IRQ 5
Jun  8 21:56:04 ix12-2 kernel: mvsas 0000:03:00.0: setting latency timer
to 64
Jun  8 21:56:05 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
491:Init flash rom ok,flash type is 0x101.
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 0 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 1 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 2 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_spi.c
527:Phy 3 SAS ADDRESS 5005043011ab0000
Jun  8 21:56:06 ix12-2 kernel: mvsas 0000:03:00.0: mvsas: PCI-E x1,
Bandwidth Usage: 2.5 Gbps
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 0 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 0 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 1 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 1 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 2 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 2 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1246:port 3 attach dev info is 0
Jun  8 21:56:08 ix12-2 kernel: /home/brian/scst/mvsas_tgt/mv_sas.c
1248:port 3 attach sas addr is 0
Jun  8 21:56:08 ix12-2 kernel: scsi17 : mvsas
Jun  8 21:56:08 ix12-2 kernel: scst: Target template mvst_scst
registered successfully
Quoted 5 lines

At this point I would have expected a new SCSI disk to appear for the virtual LUN, any thoughts? Thanks.

Brian N嫥叉靣笡y氊b瞂千v豝�)藓{.n�+壏{北�"妠ay�蕠跈�,j f＂穐殝鄗�畐ア�

⒎:+v墾妛鑚豰稛�� 珣赙zZ+凒殠娸"濟!tml=

author
#11 lore raw
Quoted 1 line · Andy Yan, on 06/11/2009 05:11 AM wrote:

No, enable target mode and then add LUN.

Why to have the race window open?

Vlad

Quoted 6 lines

-----Original Message-----
From: Vladislav Bolkhovitin [mailto:[email protected]] Sent: 2009年6月11日 2:41
To: Andy Yan
Cc: [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 11 lines
Quoted 5 lines · Andy Yan, on 06/09/2009 05:27 AM wrote:

Brian,
Please set unique SAS address for each SAS port of target controller, and make sure you do correct connection, you can get the SAS address of attaching device from "attach sas address ".Then enable target mode and add target LUN.

Do you mean "add target LUN and then enable target mode"? Otherwise an initiator can connect while there are no LUNs configured on the target and confused by it.

Quoted 2 lines

Regards
Andy Yan

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#12 lore raw

Vlad,
This design is for hot LUN changes, for Linux don't care unit attention
"report lun change", so reset phy is used to trigger the initiator to rescan
the phy when "report lun change" event is gotten, also it try to support dynamic
connection of two controller (both are initiator && target). If some good idea for resolve this issue, very welcome, thanks!

Andy Yan

-----Original Message-----
From: Vladislav Bolkhovitin [mailto:[email protected]]
Sent: 2009年6月11日 15:53
To: Andy Yan
Cc: [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 1 line · Andy Yan, on 06/11/2009 05:11 AM wrote:

No, enable target mode and then add LUN.

Why to have the race window open?

Vlad

Quoted 20 lines

-----Original Message-----
From: Vladislav Bolkhovitin [mailto:[email protected]]
Sent: 2009年6月11日 2:41
To: Andy Yan
Cc: [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [ANNOUNCE]: A target driver for Marvell 88SE64xx(3G) and 88SE94xx(6G) SAS cards

Quoted 5 lines · Andy Yan, on 06/09/2009 05:27 AM wrote:

Brian,
Please set unique SAS address for each SAS port of target controller, and make sure you do correct connection, you can get the SAS address of attaching device from "attach sas address ".Then enable target mode and add target LUN.

Do you mean "add target LUN and then enable target mode"? Otherwise an initiator can connect while there are no LUNs configured on the target and confused by it.

Quoted 2 lines

Regards
Andy Yan