Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-28 Thread Lee Duncan
> [mailto:open-iscsi@googlegroups.com <mailto:open-iscsi@googlegroups.com>] On > Behalf Of The Lee-Man > Sent: 22 December 2016 16:51 > To: open-iscsi > Subject: Re: Problem with iSCSI connected LTO-2 tape drive > > Hi David: > > I have created Issue#35

RE: Problem with iSCSI connected LTO-2 tape drive

2016-12-28 Thread David C. Partridge
[mailto:open-iscsi@googlegroups.com] On Behalf Of The Lee-Man Sent: 22 December 2016 16:51 To: open-iscsi Subject: Re: Problem with iSCSI connected LTO-2 tape drive Hi David: I have created Issue#35 for this on github. On Thursday, December 15, 2016 at 2:00:15 PM UTC-8, David C. Partridge wrote

Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-22 Thread The Lee-Man
csi@googlegroups.com [mailto:open-iscsi@googlegroups.com] *On > Behalf Of *Lee Duncan > *Sent:* 15 December 2016 19:41 > *To:* open-iscsi@googlegroups.com > *Subject:* Re: Problem with iSCSI connected LTO-2 tape drive > > > > On Dec 15, 2016, at 7:14 AM, david.partri..

RE: Problem with iSCSI connected LTO-2 tape drive

2016-12-15 Thread David C. Partridge
You’re right, it is in section 8.2. Maybe it needs to be said in 8.1.1 as well? Dave From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com] On Behalf Of Lee Duncan Sent: 15 December 2016 19:41 To: open-iscsi@googlegroups.com Subject: Re: Problem with iSCSI connected LTO-2

Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-15 Thread david . partridge
Lee, It would appear that the guilty party was: node.conn[0].timeo.noop_out_interval = 5 node.conn[0].timeo.noop_out_timeout = 5 I changed both of these to 0 for the tape device and the problem went away. Please note that the README.gz for open-scsi doesn't actually say that this is what you

Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-15 Thread david . partridge
Ulrich is correct, the scsi timeouts for tape drives are a *lot* longer. The short timeout is 900 seconds and the long timeout is 14400 seconds (4 hours). The IOCTL error message is occurring after 15 seconds, which I think points at the iSCSI layer. Cheers Dave Partridge -- You received

Antw: Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-14 Thread Ulrich Windl
>>> Lee Duncan schrieb am 14.12.2016 um 20:18 in Nachricht <8286a277-f7fe-4c7d-a944-40034a0b5...@gmail.com>: > On Dec 12, 2016, at 5:46 AM, Dave partridge wrote: >> >> I just ran a Wireshark capture on the target system of the iSCSI session for

Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-14 Thread Lee Duncan
On Dec 12, 2016, at 5:46 AM, Dave partridge 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

Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-13 Thread The Lee-Man
I am looking at these, but I haven't gotten very far. I've started examining the Unbuntu capture, and it seems normal so far. On Monday, December 12, 2016 at 5:46:17 AM UTC-8, Dave partridge wrote: > > I just ran a Wireshark capture on the target system of the iSCSI session > for a Windows

Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-12 Thread Dave partridge
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

Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-11 Thread Dave partridge
Ubuntu 16.04.1 LTS with kernel 4.8.13. Connected to target drive over 1GB ethernet. Drive is HP Ultrium 460 (Ultrium 2), firmware is F63D - which is latest). Target is served by Starwind V8 running on Windows 10 x64 Dave On Saturday, December 10, 2016 at 10:38:43 PM UTC, The Lee-Man wrote:

Re: Problem with iSCSI connected LTO-2 tape drive

2016-12-10 Thread The Lee-Man
taSegmentLength = 0 > node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144 > node.conn[0].iscsi.HeaderDigest = None > node.conn[0].iscsi.DataDigest = NoneThe return to the command prompt took a > while longer. > node.conn[0].iscsi.IFMarker = No > node.conn[0].iscsi.OFMarker = N

Problem with iSCSI connected LTO-2 tape drive

2016-12-10 Thread Dave partridge
ngth = 0 node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144 node.conn[0].iscsi.HeaderDigest = None node.conn[0].iscsi.DataDigest = NoneThe return to the command prompt took a while longer. node.conn[0].iscsi.IFMarker = No node.conn[0].iscsi.OFMarker = No # END RECORD root@Charon:/home/amonra# I'm guess

Re: Problem connecting iscsi lun: DID_TRANSPORT_DISRUPTED...

2011-01-18 Thread Pierre-Yves Langlois
Hi Mike, I made more test to debug my setup. My original setup uses a bond on 2 nic. If I only use one nic to connect to the SAN, everything works fine. The problem occurs when I use the bond... Does iscsi need a special configuration with bond or is it transparent to him? Thanks! On Mon, Jan

Re: Problem connecting iscsi lun: DID_TRANSPORT_DISRUPTED...

2011-01-18 Thread Mike Christie
On 01/18/2011 03:41 PM, Pierre-Yves Langlois wrote: Hi Mike, I made more test to debug my setup. My original setup uses a bond on 2 nic. If I only use one nic to connect to the SAN, everything works fine. The problem occurs when I use the bond... Does iscsi need a special configuration with

Re: Problem connecting iscsi lun: DID_TRANSPORT_DISRUPTED...

2011-01-17 Thread Pierre-Yves Langlois
After issuing the command echo 1 /sys/module/libiscsi/parameters/debug_libiscsi_eh,I didn't see any changes in /var/log/messages, /var/log/kern.log, /var/log/daemon.log, /var/log/debug. Do I look at the right place? On Sat, Jan 15, 2011 at 1:54 AM, Mike Christie micha...@cs.wisc.edu wrote:

Re: Problem connecting iscsi lun: DID_TRANSPORT_DISRUPTED...

2011-01-17 Thread Mike Christie
On 01/17/2011 02:26 PM, Pierre-Yves Langlois wrote: After issuing the command echo 1 /sys/module/libiscsi/parameters/debug_libiscsi_eh,I didn't see any changes in /var/log/messages, /var/log/kern.log, /var/log/daemon.log, /var/log/debug. Do I look at the right place? Did you do the echo,

Re: Problem connecting iscsi lun: DID_TRANSPORT_DISRUPTED...

2011-01-14 Thread Mike Christie
On 01/14/2011 02:40 PM, PYL wrote: I'm not able to connect to a iscsi lun. I use proxmox ve 1.7 but I have installed the kernel 2.6.36.2 to fix a bug with my network card drivers... What am I missing? Here is the output from /var/log/messages: [CODE] Jan 14 14:57:13 fl-vm01 kernel: vmbr1:

[PATCH] cxgb3i: fixed connection problem with iscsi private ip

2011-01-10 Thread kxie
[PATCH] cxgb3i: fixed connection problem with iscsi private ip From: Karen Xie k...@chelsio.com fixed the connection problem when the private iscsi ipv4 address is provisioned on the interface. Signed-off-by: Karen Xie k...@chelsio.com --- drivers/scsi/cxgbi/cxgb3i/cxgb3i.h | 18

[PATCH v2] cxgb3i: fixed connection problem with iscsi private ip

2011-01-10 Thread kxie
[PATCH v2] cxgb3i: fixed connection problem with iscsi private ip From: Karen Xie k...@chelsio.com The last one seems to have some formatting problem. Regenerated the patch. fixed the connection problem when the private iscsi ipv4 address is provisioned on the interface. Signed-off-by: Karen

Re: [PATCH v2] cxgb3i: fixed connection problem with iscsi private ip

2011-01-10 Thread Mike Christie
On 01/10/2011 06:45 PM, k...@chelsio.com wrote: [PATCH v2] cxgb3i: fixed connection problem with iscsi private ip From: Karen Xiek...@chelsio.com The last one seems to have some formatting problem. Regenerated the patch. fixed the connection problem when the private iscsi ipv4 address

Re: Problem diagnosing iscsi failure on the initiator

2010-06-16 Thread Michal Suchanek
On 16 June 2010 05:31, Mike Christie micha...@cs.wisc.edu wrote: On 06/14/2010 08:52 AM, Michal Suchanek wrote: On 13 June 2010 21:01, Mike Christiemicha...@cs.wisc.edu  wrote: On 06/12/2010 06:31 AM, Michal Suchanek wrote: Hello I tried to get an iscsi setup working so I installed

Re: Problem diagnosing iscsi failure on the initiator

2010-06-15 Thread Mike Christie
On 06/14/2010 08:52 AM, Michal Suchanek wrote: On 13 June 2010 21:01, Mike Christiemicha...@cs.wisc.edu wrote: On 06/12/2010 06:31 AM, Michal Suchanek wrote: Hello I tried to get an iscsi setup working so I installed iscsitarget and open-iscsi and tried to export a file as an iSCSI lun.

Re: Problem diagnosing iscsi failure on the initiator

2010-06-14 Thread Michal Suchanek
On 13 June 2010 21:01, Mike Christie micha...@cs.wisc.edu wrote: On 06/12/2010 06:31 AM, Michal Suchanek wrote: Hello I tried to get an iscsi setup working so I installed iscsitarget and open-iscsi and tried to export a file as an iSCSI lun. After doing so I could log in with iscsiadm but

Re: Problem diagnosing iscsi failure on the initiator

2010-06-13 Thread Mike Christie
On 06/12/2010 06:31 AM, Michal Suchanek wrote: Hello I tried to get an iscsi setup working so I installed iscsitarget and open-iscsi and tried to export a file as an iSCSI lun. After doing so I could log in with iscsiadm but I would not get any disks on the initiator. Later I discovered that

Problem diagnosing iscsi failure on the initiator

2010-06-12 Thread Michal Suchanek
Hello I tried to get an iscsi setup working so I installed iscsitarget and open-iscsi and tried to export a file as an iSCSI lun. After doing so I could log in with iscsiadm but I would not get any disks on the initiator. Later I discovered that I had a typo in the ietd.conf file and the lun