From: Rik H. <rik...@ya...> - 2006-03-26 17:18:12
|
I'm running them on the same machine to see the maximum throughput and to see what type of bottleneck the disk subsystem will give me. I'm also waiting for a 4-port 1GbE Intel NIC to make sure that the network doesn't end up being the bottleneck. Do you think there's any reason for them running on the same machine to cause a problem? Rik --- Ming Zhang <mi...@el...> wrote: > ps, any point to run them at same box? ;) > > ming > > On Sun, 2006-03-26 at 08:30 -0800, Rik Herrin wrote: > > I am going to try it with open-iscsi and > core-iscsi to > > see if this issue is initiator-specific or IET > > specific. In the meantime, I configured a 4-disk > RAID > > 0 SATA configuration and set it as the device > exported > > by IET. Without the iSCSI layer (without running > > either ietd or iscsi-linux), I saw write > throughput of > > about 212 MB/s. When I started IET and > linux-iscsi > > and ran the sequential write test, I am now > getting > > the following errors: > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 445 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 446 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 447 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 448 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 449 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 450 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 451 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 452 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 453 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 454 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 455 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 456 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 457 with return code > = > > 0x20000 > > Mar 26 18:37:28 localhost kernel: > iscsi-sfnet:host5: > > Failing command cdb 0x2a task 458 with return code > = > > 0x20000 > > ... [a lot more of the above] > > > > followed by: > > > > Mar 26 18:37:25 localhost kernel: > > execute_task_management(1177) 1e2 1 bd010000 > > Mar 26 18:37:25 localhost kernel: cmnd_abort(1114) > 1bd > > 1 0 42 131072 0 0 > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > task mgmt itt 482 rejected (0x1) > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > Sending ABORT TASK for task itt 446 > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > Waking tx_thread to send task mgmt function itt > 483 > > Mar 26 18:37:25 localhost kernel: > > execute_task_management(1177) 1e3 1 be010000 > > Mar 26 18:37:25 localhost kernel: cmnd_abort(1114) > 1be > > 1 0 42 131072 0 0 > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > task mgmt itt 483 rejected (0x1) > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > Sending ABORT TASK for task itt 447 > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > Waking tx_thread to send task mgmt function itt > 484 > > Mar 26 18:37:25 localhost kernel: > > execute_task_management(1177) 1e4 1 bf010000 > > Mar 26 18:37:25 localhost kernel: cmnd_abort(1114) > 1bf > > 1 0 42 131072 0 0 > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > task mgmt itt 484 rejected (0x1) > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > Sending ABORT TASK for task itt 448 > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > Waking tx_thread to send task mgmt function itt > 485 > > Mar 26 18:37:25 localhost kernel: > > execute_task_management(1177) 1e5 1 c0010000 > > Mar 26 18:37:25 localhost kernel: cmnd_abort(1114) > 1c0 > > 1 0 42 131072 0 0 > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > task mgmt itt 485 rejected (0x1) > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > Sending ABORT TASK for task itt 449 > > Mar 26 18:37:25 localhost kernel: > iscsi-sfnet:host5: > > Waking tx_thread to send task mgmt function itt > 486 > > Mar 26 18:37:25 localhost kernel: > > execute_task_management(1177) 1e6 1 c1010000 > > .. [some more errors] > > > > > > scsi5 (0:0): rejecting I/O to offline device > > scsi5 (0:0): rejecting I/O to offline device > > scsi5 (0:0): rejecting I/O to offline device > > scsi5 (0:0): rejecting I/O to offline device > > scsi5 (0:0): rejecting I/O to offline device > > > > real 6m1.986s > > user 0m0.006s > > sys 0m1.682s > > > > Rik > > > > > > --- Ming Zhang <mi...@el...> wrote: > > > > > can u try open-iscsi? > > > > > > ming > > > > > > On Sun, 2006-03-26 at 05:12 -0800, Rik Herrin > wrote: > > > > Hi, > > > > I'm not sure if this is an iscsi-linux or > IET > > > issue, > > > > so I decided to post it on both mailing lists. > I > > > have > > > > the following environment: > > > > > > > > Environment: > > > > RHEL v4 U2 > > > > IET v 0.4.12-6 > > > > (iscsitarget-kernel-smp-0.4.12-6_2.6.9_22.EL > and > > > > iscsitarget-0.4.12-6) > > > > iscsi-initiator-utils-4.0.3.0-2 > > > > > > > > To get a quick idea of how much overhead > the > > > iSCSI > > > > initiator / target will add to my I/O, I > performed > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |