ups.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 for this on github.
>
> On Thursday, De
[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
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...@per
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
On Dec 15, 2016, at 7:14 AM, david.partri...@perdrix.co.uk wrote:
>
> 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.
Excel
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 n
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 th
>>> 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
> a Windows initiator connecting the tape and then
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 capture for the WIndows ini
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 initi
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 kno
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:
>
What is your setup? What OS and version are you running on, what is your
transport, and what tape drive are you using?
On Saturday, December 10, 2016 at 9:24:33 AM UTC-8, Dave partridge wrote:
>
> I did:
>
> root@Charon:/home/amonra# mt -f /dev/st0 fsf 1
> mt: /dev/st0: rmtioctl failed: Input/ou
13 matches
Mail list logo