logo       

Re: open-iscsi + iet: msg#00269

Subject: Re: open-iscsi + iet
On Mon, 2005-07-25 at 11:06 -0500, Brian Wolfe wrote:
> iscsi3:~# iscsi-ls
> *******************************************************************************
> SFNet iSCSI Driver Version ...4:0.2(15-Mar-2005)
> *******************************************************************************

this is sfnet right? what linux kernel u use then?


> 
> ietadm version 0.4.9
> 
> Seems to be working here. 
> 
> I've gotten two oopses in the last week though not related to ietd's
> compatibility...
> 
> on command abort.

this abort is solved in later version i remember.


> 
> execute_task_management(1161) c8591c 1 f758c800
> cmnd_abort(1104) c858f7 1 0 42 20480 0 0
> execute_task_management(1161) c8591d 2 ffffffff
> BUG
> at /home/ahzz/Projects/Production/disk/iscsitarget-0.4.9/kernel/iscsi.c:225 
> assert(list_empty(&cmnd->list))
>  [<d89568df>] iscsi_cmnd_init_write+0x6f/0x80 [iscsi_trgt]
>  [<d8959d72>] recv+0xf2/0x3e0 [iscsi_trgt]
>  [<d895999d>] is_data_available+0x3d/0x60 [iscsi_trgt]
>  [<d895a927>] process_io+0x27/0xa0 [iscsi_trgt]
>  [<d895ac5f>] istd+0x8f/0xf0 [iscsi_trgt]
>  [<d895abd0>] istd+0x0/0xf0 [iscsi_trgt]
>  [<c012b84a>] kthread+0xaa/0xb0
>  [<c012b7a0>] kthread+0x0/0xb0
>  [<c01012fd>] kernel_thread_helper+0x5/0x18
> ------------[ cut here ]------------
> 
> and if the disk IO fails (bad sector) I ended up with the following
> oops...

yes, this is really a problem. currently we do not consider it yet.


> 
> hdi: dma_timer_expiry: dma status == 0x21
> hdi: DMA timeout error
> hdi: dma timeout error: status=0xd0 { Busy }
> 
> ide: failed opcode was: unknown
> hdi: DMA disabled
> PDC202XX: Primary channel reset.
> execute_task_management(1161) d8d388 1 6ad3d800
> cmnd_abort(1104) d8d36a 1 0 40 0 0 0
> execute_task_management(1161) d8d389 2 ffffffff
> BUG
> at /home/ahzz/Projects/Production/disk/iscsitarget-0.4.9/kernel/iscsi.c:225 
> assert(list_empty(&cmnd->list))
>  [<d89568df>] iscsi_cmnd_init_write+0x6f/0x80 [iscsi_trgt]
>  [<d8959d72>] recv+0xf2/0x3e0 [iscsi_trgt]
>  [<d895999d>] is_data_available+0x3d/0x60 [iscsi_trgt]
>  [<d895a927>] process_io+0x27/0xa0 [iscsi_trgt]
>  [<d895ac5f>] istd+0x8f/0xf0 [iscsi_trgt]
>  [<d895abd0>] istd+0x0/0xf0 [iscsi_trgt]
>  [<c012b84a>] kthread+0xaa/0xb0
>  [<c012b7a0>] kthread+0x0/0xb0
>  [<c01012fd>] kernel_thread_helper+0x5/0x18
> ------------[ cut here ]------------
> kernel BUG at <bad filename>:44267!
> invalid operand: 0000 [#1]
> Modules linked in: iscsi_trgt 3c59x 8139too
> CPU:    0
> EIP:    0060:[<d89568df>]    Not tainted VLI
> EFLAGS: 00010286   (2.6.11-bbr) 
> EIP is at iscsi_cmnd_init_write+0x6f/0x80 [iscsi_trgt]
> eax: d6ac7ffd   ebx: ccfc3460   ecx: c0420018   edx: 00000000
> esi: d6ac7f50   edi: 00000001   ebp: c80c9710   esp: d6ac7f40
> ds: 007b   es: 007b   ss: 0068
> Process istd2 (pid: 1354, threadinfo=d6ac6000 task=d6a3eae0)
> Stack: d8960b31 d8961520 000000e1 d8960b4d d6ac7f50 d6ac7f50 d6a98800
> 00000000 
>        d8959d72 ccfc3460 00000286 d6a3eae0 d6ac7f7c d895999d 00000000
> 00000000 
>        d6a98800 d6ac6000 00000000 d70b8c00 d895a927 d6a98800 d70b8d58
> d6ac6000 
> Call Trace:
>  [<d8959d72>] recv+0xf2/0x3e0 [iscsi_trgt]
>  [<d895999d>] is_data_available+0x3d/0x60 [iscsi_trgt]
>  [<d895a927>] process_io+0x27/0xa0 [iscsi_trgt]
>  [<d895ac5f>] istd+0x8f/0xf0 [iscsi_trgt]
>  [<d895abd0>] istd+0x0/0xf0 [iscsi_trgt]
>  [<c012b84a>] kthread+0xaa/0xb0
>  [<c012b7a0>] kthread+0x0/0xb0
>  [<c01012fd>] kernel_thread_helper+0x5/0x18
> Code: 04 24 31 0b 96 d8 b9 4d 0b 96 d8 ba e1 00 00 00 89 4c 24 0c b8 20
> 15 96 d8
>  89 54 24 08 89 44 24 04 e8 46 2c 7c e7 e8 f1 d3 7a e7 <0f> 0b eb ac 8d
> b6 00 00
>  00 00 8d bc 27 00 00 00 00 55 57 56 53 
>  ide4: reset timed-out, status=0x80
> hdi: status timeout: status=0x80 { Busy }
> 
> ide: failed opcode was: unknown
> PDC202XX: Primary channel reset.
> hdi: drive not ready for command
> ide4: reset: success
> 
> 
> On Mon, 2005-07-25 at 10:57 -0400, Ming Zhang wrote:
> > Hi folks
> > 
> > Any idea on latest status about the stability issue of IET+open-iscsi?
> > 
> > thx!
> > 
> > Ming
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Iscsitarget-devel mailing list
> > Iscsitarget-devel@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf


<Prev in Thread] Current Thread [Next in Thread>