On Dec 12, 2016, at 5:46 AM, Dave partridge <[email protected]> wrote: > > I just ran a Wireshark capture on the target system of the iSCSI session for > a Windows initiator connecting the tape and then issuing an FSF. I then did > the same for the Ubuntu open-iscsi initiator. > > The capture for the WIndows initiator looks pretty much as I would expect > (given my limited knowledge of the iSCSI protocols). > > The Ubuntu/open-iscsi capture has all sorts of odd stuff like logins being > sent to the target every 15 seconds whle the FSF is being processed. > Definitely borked I think. > > Do any of the open-iscsi folk watch this forum or am I talking to myself? > > Dave
Hi Dave: I think you are right — the problem is the timeout. The default timeout on many systems (like SUSE that I work on) is set to 60 seconds for a SCSI command. And it looks like the tape drive took about 82 seconds to skip forward a file on your Windows trace. Try setting the timeout to 90 seconds? The open-iscsi README talks about how to manually set the system SCSI timeout to longer (since this isn’t an iSCSI thing). Also, you may want to disable the Ping/NOOPs that open-iscsi is setting. This is also discussed in the README file. I’d try setting them both to 0 to get them out of the way. It looks like the tape drive does not respond to the NOOP ping when it is busy for 80+ seconds skipping forward one file. — Lee Duncan -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
