It looks like the Linux initiator asked for 12 bytes of "read capacity 16" data and the Solaris target returned a full 32 bytes response.
From a quick glance at the iSCSI target code it appears that sbc_read_capacity16 should pass "rep_size" to trans_send_datain() instead of io->da_data_len. Peter Dunlap wrote: > Well... I don't see anything blatantly wrong with either the "Read > Capacity 16" request or the corresponding response. For some reason the > Linux initiator is repeatedly dropping the connection shortly after the > "Read Capacity 16" response. The sequence goes like this: > > 1. Login > 2. Read Capacity 16 > 3. Read Capacity 16 response > 4. TCP RST from initiator > (then the cycle starts over with the login). > > I'll keep looking at it. > > Nathanael Burton wrote: > >> I performed a Wireshark capture between the Linux client(shuttle - >> 10.1.0.200) and the Solaris server(filestore - 10.1.0.40). Attached is the >> capture session, which produces the "READ CAPACITY(16) failed" error. >> >> Thanks, >> >> mathrock >> >> >> This message posted from opensolaris.org >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> storage-discuss mailing list >> [email protected] >> http://mail.opensolaris.org/mailman/listinfo/storage-discuss >> >> > > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > > _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
