Mike Christie wrote: > Olaf Kirch wrote: >> Hi, >> >> I tried to use the iSCSI initiator with iscsitarget on 2.6.21-rc6 today, >> with rather mixed results. >> >> I could log in okay, and a device would appear. Trying to mount >> that device would hang though: >> >> kernel: iscsi: ctask enq [read cid 0 sc df57e500 cdb 0x28 itt 0x1c len 4096 cmdsn 29 win 33] >> kernel: iscsi: cmdrsp [op 0x25 cid 0 itt 0x1c len 0] >> ... >> kernel: iscsi: ctask enq [read cid 0 sc df57e500 cdb 0x28 itt 0x2b len 4096 cmdsn 44 win 33] >> kernel: iscsi: cmdrsp [op 0x25 cid 0 itt 0x2b len 0] >> kernel: kjournald starting. Commit interval 5 seconds >> kernel: iscsi: ctask enq [write cid 0 sc df57e500 cdb 0x2a itt 0x2c len 4096 cmdsn 45 win 33] >> >> Nothing in the logs. tcpdump shows lots of data being transmitted, and tracing >> iscsitarget shows a storm of data_out commands being received. >> > > Could you send the trace? It is weird that we would get a storm of data > out commands for a IO that was only 4096 bytes (assuming part of the log > did not get cut off and the above line is the last one). Oh yeah, does reverting the endien patches http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commitdiff;h=b4377356450e2358f5f92d34f130d6cb6574bf76 make any difference? - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
