[stgt] Fwd: Re: targets.conf problem, setting up tape drives

[Albert Pauw]

I changed /root/tapes to /root/btapes, and indeed using tgt-admin -e -v 
the tape drives are
defined first now.

However, login into the target, I see this in dmesg:

scsi2 : iSCSI Initiator over TCP/IP
  connection1:0: detected conn error (1019)
scsi 2:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
scsi 2:0:0:0: Attached scsi generic sg2 type 12
scsi 2:0:0:1: Sequential-Access HP       LTO3 ULTRIUM     0001 PQ: 0 ANSI: 5
scsi 2:0:0:1: Attached scsi generic sg3 type 1
scsi 2:0:0:2: Sequential-Access HP       LTO3 ULTRIUM     0001 PQ: 0 ANSI: 5
scsi 2:0:0:2: Attached scsi generic sg4 type 1
scsi 2:0:0:3: Sequential-Access HP       LTO3 ULTRIUM     0001 PQ: 0 ANSI: 5
scsi 2:0:0:3: Attached scsi generic sg5 type 1
scsi 2:0:0:4: Medium Changer    STK      L700             0001 PQ: 0 ANSI: 5
scsi 2:0:0:4: Attached scsi generic sg6 type 8
SCSI Media Changer driver v0.25
Driver 'ch' needs updating - please use bus_type methods
ch0: type #1 (mt): 0x0+0 [medium transport]
ch0: type #2 (st): 0x0+0 [storage]
ch0: type #3 (ie): 0x0+0 [import/export]
ch0: type #4 (dt): 0x0+0 [data transfer]
ch0: INITIALIZE ELEMENT STATUS, may take some time ...
ch0: ... finished
ch 2:0:0:4: Attached scsi changer ch0
st: Version 20081215, fixed bufsize 32768, s/g segs 256
Driver 'st' needs updating - please use bus_type methods
st 2:0:0:1: Attached scsi tape st0
st 2:0:0:1: st0: try direct i/o: yes (alignment 1 B)
st 2:0:0:2: Attached scsi tape st1
st 2:0:0:2: st1: try direct i/o: yes (alignment 1 B)
st 2:0:0:3: Attached scsi tape st2
st 2:0:0:3: st2: try direct i/o: yes (alignment 1 B)
osst :I: Tape driver with OnStream support version 0.99.4
osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
Driver 'osst' needs updating - please use bus_type methods

But

[root at orange ~]# mtx -f /dev/changer status
(after some 2 minutes of waiting)
no Data Transfer Element reported

and in dmesg, the following error was added

  connection1:0: ping timeout of 5 secs expired, last rx 4294857161, 
last ping 4294862161, now 4294867161
  connection1:0: detected conn error (1011)
  session1: session recovery timed out after 120 secs

So, things are not good.

On 10/26/2009 05:09 PM, Tomasz Chmielewski wrote:
>
>  I think I see where the problem is.
>
>  Since these are hashes, they have no defined order.
>
>  As such, they will be "ordered" alphabetically.
>
>  /root/smc comes before /root/tapes, so this is what you get.
>
>
>  I wonder how it can be solved.
>
>  Hmm.
>
>
Tell you what, I'll change /root/tapes to /root/btapes and see if it
actually works fine,
then we know for sure it is only this problem.

I'll let you know how it went.

Albert

--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html