| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Sorry Ming. The previously attached log was with 8K specified in the core-iscsi configuration file. Here's one with the configuration file (/etc/sysconfig/initiator) w/: CHANNEL="0 1 lo 127.0.0.1 3260 0" --- Ming Zhang <mingz@xxxxxxxxxxx> wrote: > > On Mon, 2006-03-27 at 07:33 -0800, Rik Herrin wrote: > > (This is the exact same email I sent 10 minutes > ago. > > I just forgot to add the tcpdump output.) > > > > "The problem with the above 2 is that Core-ISCSI > is > > trying to send 32k PDUs while IET only accepts 8K > > PDUs." > > i forgot since iet which version, we correctly > handle this. so i want to > see u tcpdump trace for detail. if u adjust the ini > parameter, it is ok > well. but a tcpdump log before u adjusting this > parameter will be > useful. > > i need a log captured with "tcpdump -s1600 -w log" > and send us the log, > or bziped if it is large. > > ming > > > > > So I replaced it with the following: > > > > CHANNEL="0 1 lo 127.0.0.1 3260 0 > > AuthMethod=None;MaxRecvDataSegmentLength=8192 > > nopout_timeout=5" > > > > which should send 8K PDUs instead. In either > case, I > > added a tcpdump of the login process at the end of > my > > email. I then ran the same dd as before which > should > > write 500 MB of sequential data onto the iSCSI > target. > > It's talking a very long time to dd 500M onto the > > iSCSI target disc and looking at top, it gives me > the > > following: > > > > istd1 taking 99.9% CPU with them split up as 50.1% > sy > > and 49.9% wait > > > > Looking into /var/log/messages, I see messages > such > > as: > > > > Mar 27 17:25:21 localhost kernel: iCHANNEL[0] - No > > defined iSCSI Authentication Methods, skipping > > SecurityNegotiation phase. Mar 27 17:25:46 > localhost > > kernel: iscsi_login_rx_data:54: ***ERROR*** > rx_data > > returned -512, expecting 48. Mar > 27 > > 17:25:46 localhost kernel: > > iscsi_initiator_start_negotiation:754: ***ERROR*** > > iSCSI Login negotiation failed. Mar 27 > > 17:25:46 localhost kernel: > > iscsi_handle_authetication:108: ***ERROR*** > > sock_recvmsg() returned 0 Mar > 27 > > 17:25:48 localhost kernel: iCHANNEL[0] - No > defined > > iSCSI Authentication Methods, skipping > > SecurityNegotiation phase. > > Mar 27 17:26:13 localhost kernel: > > iscsi_login_rx_data:54: ***ERROR*** rx_data > returned > > -512, expecting 48. > > Mar 27 17:26:13 localhost kernel: > > iscsi_initiator_start_negotiation:754: ***ERROR*** > > iSCSI Login negotiation failed. > > Mar 27 17:26:13 localhost kernel: > > iscsi_handle_authetication:108: ***ERROR*** > > sock_recvmsg() returned 0 > > Mar 27 17:26:15 localhost kernel: iCHANNEL[0] - No > > defined iSCSI Authentication Methods, skipping > > SecurityNegotiation phase. > > ............. > > > > Could it be, as you mentioned in a previous mail, > that > > since IET doesn't get back to the initiator and > tell > > it that it's successfully written the data, the > > core-iscsi initiator believes that the connection > is > > lost and tries to start a new session and fails > > because there's already the old session and IET > > doesn't support MCS? I'm off to try open-iscsi. > > Thanks for your help. > > > > Rik Herrin > > > > TCP Dump of Login: > > > > 17:59:49.597309 IP localhost.localdomain.32771 > > > localhost.localdomain.3260: S > 1001746800:1001746800(0) > > win 32767 <mss 16396,sackOK,timestamp 179287 > > 0,nop,wscale 5> > > 17:59:49.597760 IP localhost.localdomain.3260 > > > localhost.localdomain.32771: S > 990883816:990883816(0) > > ack 1001746801 win 32767 <mss > 16396,sackOK,timestamp > > 179287 179287,nop,wscale 5> > > 17:59:49.597789 IP localhost.localdomain.32771 > > > localhost.localdomain.3260: . ack 1 win 1024 > > <nop,nop,timestamp 179287 179287> > > 17:59:49.597804 IP localhost.localdomain.32771 > > > localhost.localdomain.3260: P 1:233(232) ack 1 win > > 1024 <nop,nop,timestamp 179287 179287> > > 17:59:49.597819 IP localhost.localdomain.3260 > > > localhost.localdomain.32771: . ack 233 win 1058 > > <nop,nop,timestamp 179287 179287> > > 17:59:49.597352 IP localhost.localdomain.3260 > > > localhost.localdomain.32771: P 1:109(108) ack 233 > win > > 1058 <nop,nop,timestamp 179287 179287> > > 17:59:49.597498 IP localhost.localdomain.32771 > > > localhost.localdomain.3260: . ack 109 win 1024 > > <nop,nop,timestamp 179287 179287> > > 17:59:49.597814 IP localhost.localdomain.32771 > > > localhost.localdomain.3260: P 233:297(64) ack 109 > win > > 1024 <nop,nop,timestamp 179287 179287> > > 17:59:49.597957 IP localhost.localdomain.3260 > > > localhost.localdomain.32771: P 109:249(140) ack > 297 > > win 1058 <nop,nop,timestamp 179288 179287> > > 17:59:49.598540 IP localhost.localdomain.32771 > > > localhost.localdomain.3260: P 297:345(48) ack 249 > win > > 1024 <nop,nop,timestamp 179288 179288> > > 17:59:49.598590 IP localhost.localdomain.3260 > > > localhost.localdomain.32771: P 249:297(48) ack 345 > win > > 1058 <nop,nop,timestamp 179288 179288> > > 17:59:49.598679 IP localhost.localdomain.32771 > > > localhost.localdomain.3260: F 345:345(0) ack 297 > win > > 1024 <nop,nop,timestamp 179288 179288> > > 17:59:49.598715 IP localhost.localdomain.32772 > > > localhost.localdomain.3260: S > 991579803:991579803(0) > > win 32767 <mss 16396,sackOK,timestamp 179288 > > 0,nop,wscale 5> > > 17:59:49.598730 IP localhost.localdomain.3260 > > > localhost.localdomain.32772: S > > 1003662361:1003662361(0) ack 991579804 win 32767 > <mss > > 16396,sackOK,timestamp 179288 179288,nop,wscale 5> > > 17:59:49.598746 IP localhost.localdomain.32772 > > > localhost.localdomain.3260: . ack 1 win 1024 > > <nop,nop,timestamp 179288 179288> > > 17:59:49.598825 IP localhost.localdomain.32772 > > > localhost.localdomain.3260: P 1:533(532) ack 1 win > > 1024 <nop,nop,timestamp 179288 179288> > > 17:59:49.598846 IP localhost.localdomain.3260 > > > localhost.localdomain.32772: . ack 533 win 1058 > > <nop,nop,timestamp 179288 179288> > > 17:59:49.598893 IP localhost.localdomain.3260 > > > localhost.localdomain.32771: F 297:297(0) ack 346 > win > > 1058 <nop,nop,timestamp 179289 179288> > > 17:59:49.598902 IP localhost.localdomain.32771 > > > localhost.localdomain.3260: . ack 298 win 1024 > > <nop,nop,timestamp 179289 179289> > > 17:59:49.599141 IP localhost.localdomain.3260 > > > localhost.localdomain.32772: P 1:353(352) ack 533 > win > > 1058 <nop,nop,timestamp 179289 179288> > > 17:59:49.599160 IP localhost.localdomain.32772 > > > localhost.localdomain.3260: . ack 353 win 1058 > > <nop,nop,timestamp 179289 179289> > > 17:59:49.599520 IP localhost.localdomain.32772 > > > localhost.localdomain.3260: P 533:581(48) ack 353 > win > > 1058 <nop,nop,timestamp 179289 179289> > > 17:59:49.599592 IP localhost.localdomain.3260 > > > localhost.localdomain.32772: P 353:401(48) ack 581 > win > > 1058 <nop,nop,timestamp 179289 179289> > > 17:59:49.599604 IP localhost.localdomain.3260 > > > localhost.localdomain.32772: P 401:437(36) ack 581 > win > > 1058 <nop,nop,timestamp 179289 179289> > > 17:59:49.599707 IP localhost.localdomain.32772 > > > localhost.localdomain.3260: P 581:629(48) ack 437 > win > > 1058 <nop,nop,timestamp 179289 179289> > > 17:59:49.599750 IP localhost.localdomain.3260 > > > localhost.localdomain.32772: P 437:485(48) ack 629 > win > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Attachment:
log
Description: 21971069-log
[IP Storage] [IETF] [Linux SCSI] [iSCSI Book] [Linux Resources] [Yosemite News] [Photo] [Home] [IETF Announcements] [IETF Discussion] [SCSI Hardware]