Menu
▾
▴
Re: [Scst-devel] mvsas target mode support in kernel 2.6.36.2
|
From: Andy Y. <ay...@ma...> - 2010-12-30 08:46:22
|
Vlad,
Can you help to answer the question with these debug info, thanks!
Regards,
Andy Yan
-----Original Message-----
From: Jayaraman Thiruvady [mailto:jay...@gm...]
Sent: 2010年12月30日 16:13
To: Andy Yan
Cc: scs...@li...
Subject: Re: [Scst-devel] mvsas target mode support in kernel 2.6.36.2
Hi Andy Yan,
I got my machine setup as follows
Target machine:
Latest for scst for svn trunk, with marvel mvsas target mode
driver with the patches we did. ( kernel 2.6.36.2 )
11:00.0 SCSI storage controller: Marvell Technology Group Ltd.
MV64460/64461/64462 System Controller, Revision B (rev 01)
Created a LV of 30G in LVM and mapped to scst devices as vdisk (
block device )
Initiator machine:
Areca SAS card (marvel chip) crossed wired to Target machine
(Supermicro - AOC-SASLP-MV8).
When initiator starts, it fails to identify target drive mapped and
dmesg is as below
Dec 30 16:00:44 pentagon-server kernel: [ 925.480199] [0]:
__scst_check_blocked_dev:6622:cmd ffff8801b12dcc00 (tag 22016),
blocking further cmds due to possible double reset UA (dev
ffff8803308d7000)
Dec 30 16:00:44 pentagon-server kernel: [ 925.480206] [0]:
scst_block_dev:6563:Device BLOCK(new 1), dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 925.480217] [2103]:
scst_check_unblock_dev:563:cmd ffff8801b12dcc00 (tag 22016):
unblocking dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 925.480222] [0]:
scst_unblock_dev:6571:Device UNBLOCK(new 0), dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 925.676914] [0]:
__scst_check_blocked_dev:6622:cmd ffff8801b12dcc00 (tag 22016),
blocking further cmds due to possible double reset UA (dev
ffff8803308d7000)
Dec 30 16:00:44 pentagon-server kernel: [ 925.676919] [0]:
scst_block_dev:6563:Device BLOCK(new 1), dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 925.676930] [0]: dev_vdisk:
vdisk_init_thr_data:918:***ERROR***:
filp_open(/dev/mapper/pentagondisk-Win2k8) returned an error -2
Dec 30 16:00:44 pentagon-server kernel: [ 925.676937] [0]:
scst_check_unblock_dev:563:cmd ffff8801b12dcc00 (tag 22016):
unblocking dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 925.676941] [0]:
scst_unblock_dev:6571:Device UNBLOCK(new 0), dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 925.880086] [0]:
__scst_check_blocked_dev:6622:cmd ffff8801b12dcc00 (tag 22016),
blocking further cmds due to possible double reset UA (dev
ffff8803308d7000)
Dec 30 16:00:44 pentagon-server kernel: [ 925.880091] [0]:
scst_block_dev:6563:Device BLOCK(new 1), dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 925.880101] [0]: dev_vdisk:
vdisk_init_thr_data:918:***ERROR***:
filp_open(/dev/mapper/pentagondisk-Win2k8) returned an error -2
Dec 30 16:00:44 pentagon-server kernel: [ 925.880107] [0]:
scst_check_unblock_dev:563:cmd ffff8801b12dcc00 (tag 22016):
unblocking dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 925.880111] [0]:
scst_unblock_dev:6571:Device UNBLOCK(new 0), dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 926.084076] [0]:
__scst_check_blocked_dev:6622:cmd ffff8801b12dcc00 (tag 22016),
blocking further cmds due to possible double reset UA (dev
ffff8803308d7000)
Dec 30 16:00:44 pentagon-server kernel: [ 926.084082] [0]:
scst_block_dev:6563:Device BLOCK(new 1), dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 926.084092] [0]: dev_vdisk:
vdisk_init_thr_data:918:***ERROR***:
filp_open(/dev/mapper/pentagondisk-Win2k8) returned an error -2
Dec 30 16:00:44 pentagon-server kernel: [ 926.084097] [0]:
scst_check_unblock_dev:563:cmd ffff8801b12dcc00 (tag 22016):
unblocking dev ffff8803308d7000
Dec 30 16:00:44 pentagon-server kernel: [ 926.084101] [0]:
scst_unblock_dev:6571:Device UNBLOCK(new 0), dev ffff8803308d7000
I tired to map the same vdisk setup to a iscsi-target with open-iscsi
as initiator and that works.
I also tried to map a usb thumb drive as a scst disk device to the
mvsas target. The acera sas card identify it as scst drive and its
working.
So what could be the issue with vdisk setup? May i missing something.
Regards,
Jayaraman.T
On Wed, Dec 29, 2010 at 1:58 PM, Andy Yan <ay...@ma...> wrote:
> Jayaraman.T,
> Please replace the function with following code
>
> int mvs_slave_configure(struct scsi_device *sdev)
> {
> struct domain_device *dev = sdev_to_domain_dev(sdev);
> int ret = sas_slave_configure(sdev);
>
> if (ret)
> return ret;
>
> if (!dev_is_sata(dev))
> sas_change_queue_depth(sdev,
> MVS_QUEUE_SIZE,
> SCSI_QDEPTH_DEFAULT);
> return 0;
> }
>
> Regards,
> Andy Yan
>
> -----Original Message-----
> From: Jayaraman Thiruvady [mailto:jay...@gm...]
> Sent: 2010年12月29日 12:06
> To: scs...@li...
> Cc: Andy Yan
> Subject: Re: [Scst-devel] mvsas target mode support in kernel 2.6.36.2
>
> patched it.
>
> sas_change_queue_depth(sdev, MVS_QUEUE_SIZE) ->
> sas_change_queue_depth(sdev, MVS_QUEUE_SIZE, SCSI_QDEPTH_DEFAULT);
> SAM_GOOD -> SAM_STAT_GOOD
> SAM_CHECK_COND -> SAM_STAT_CHECK_CONDITION
>
> Regards,
> Jayaraman.T
>
> On Wed, Dec 29, 2010 at 11:23 AM, Jayaraman Thiruvady
> <jay...@gm...> wrote:
>> Hi,
>>
>> I have a Marvel card for Supermicro - AOC-SASLP-MV8 and i want use
>> them as scst target mode.
>>
>> 11:00.0 SCSI storage controller: Marvell Technology Group Ltd.
>> MV64460/64461/64462 System Controller, Revision B (rev 01)
>>
>> I am using vanilla kernel 2.6.36.2 and when i try compiling
>> "mvsas_tgt" target mode code ( scst svn truck ), i get the following
>> errors
>>
>> make -C /lib/modules/2.6.36.2/build
>> SUBDIRS=/home/jayaraman/scst/mvsas_tgt BUILD_INI=m
>> make[1]: Entering directory `/usr/src/linux-2.6.36.2'
>> CC [M] /home/jayaraman/scst/mvsas_tgt/mv_sas.o
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c: In function ‘mvs_slave_configure’:
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c:423: error: too few arguments
>> to function ‘sas_change_queue_depth’
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c: In function
>> ‘mvs_exec_internal_tmf_task’:
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c:1503: error: ‘SAM_GOOD’
>> undeclared (first use in this function)
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c:1503: error: (Each undeclared
>> identifier is reported only once
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c:1503: error: for each function
>> it appears in.)
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c: In function ‘mvs_sata_done’:
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c:1744: error: ‘SAM_GOOD’
>> undeclared (first use in this function)
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c: In function ‘mvs_slot_err’:
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c:1770: error: ‘SAM_CHECK_COND’
>> undeclared (first use in this function)
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c: In function ‘mvs_slot_complete’:
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c:1867: error: ‘SAM_GOOD’
>> undeclared (first use in this function)
>> /home/jayaraman/scst/mvsas_tgt/mv_sas.c:1876: error: ‘SAM_CHECK_COND’
>> undeclared (first use in this function)
>> make[2]: *** [/home/jayaraman/scst/mvsas_tgt/mv_sas.o] Error 1
>> make[1]: *** [_module_/home/jayaraman/scst/mvsas_tgt] Error 2
>> make[1]: Leaving directory `/usr/src/linux-2.6.36.2'
>> make: *** [all] Error 2
>>
>> I have been using this card in target mode in the kernel - version
>> 2.6.33.4 and since i updated my kernel to 2.6.36.2, i get into this
>> issue.
>>
>> Looks like mvsas target mode is not supporting latest kernel. Please
>> let me know which of the latest version of kernel supports this card?
>> Or can i get any patches to fix this problem?
>>
>> Thanks in advance for your reply.
>>
>> Regards,
>> Jayaraman.T
>>
>
|