Re: Abort Task ?

["BERTRAND Joël" <joel.bertrand@systella.fr>]

Ming Zhang wrote:
> On Thu, 2007-10-18 at 11:33 -0400, Ross S. W. Walker wrote:
>> BERTRAND Joël wrote:
>>> BERTRAND Joël wrote:
>>>> BERTRAND Joël wrote:
>>>>> 	Hello,
>>>>>
>>>>> 	When I try to create a raid1 volume over iscsi, process 
>>> aborts with :
>>>>> - on target side:
>>>>>
>>>>> iscsi_trgt: cmnd_abort(1156) 29 1 0 42 57344 0 0
>>>>> iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by 
>>> sid:630024457682948 
>>>>> (Unknown Task)
>>>> 	Next run:
>>>> iscsi_trgt: cmnd_abort(1156) 13 1 0 42 57344 0 0
>>>> iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by 
>>> sid:630058817421315 
>>>> (Unknown Task)
>>>>
>>>> 	You can see that both lines are very similar. I shall 
>>> try to use 
>>>> blockio instead fileio.
>>> 	With blockio, I got the following message...
>>>
>>> iscsi_trgt: cmnd_abort(1156) c 1 0 42 8192 0 0
>>> iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by 
>>> sid:630024457682946 
>>> (Unknown Task)
>>>
>>> Command is the same. What is the signification of 1156 ?
>> Both outputs are from the same Abort Task management function
>> the 1156 refers to the line in iscsi.c where the debug printf
>> was issued.
>>
>> The other is the more verbose informative message that says
>> an Abort Task command was issued, but the task was not found.
> 
> pure guess, this might because the sparc64 you are using.
> 
> could you export a NULLIO target and do some intensive io tests? sort
> out these platform issues first...

	I can format serveral times (mkfs.ext3) a 1.5 TB volume over iSCSI 
without any trouble. I can read and write on this virtual disk without 
any trouble.

	Now, I have configured ietd with :

Lun 0 Sectors=1464725758,Type=nullio

and I run on initiator side :

Root gershwin:[/dev] > dd if=/dev/zero of=/dev/sdj bs=8192
479482+0 records in
479482+0 records out
3927916544 bytes (3.9 GB) copied, 153.222 seconds, 25.6 MB/s

Root gershwin:[/dev] > dd if=/dev/zero of=/dev/sdj bs=8192

	I'm waitinfor a crash. No one when I write these lines.	I suspect an 
interaction between raid and iscsi.

	Regards,

	JKB

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Iscsitarget-devel mailing list
Iscsitarget-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel