On Sep 29, 9:03 am, Konrad Rzeszutek <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 28, 2008 at 06:58:36AM -0700, Nick wrote:
> > I'm trying to use open-iscsi to connect to an iSCSI-based tape
> > library.  The library has two drives, so there are three IDs.
> > Unfortunately, the library is picky about having the same SCSI IDs as
> > are configured directly on the library, which means on the iSCSI
> > client end I need to make sure that the devices show up with those
> > same IDs.  This presents two problems:
> > 1) Each of the devices is presented as a separate iSCSI target.  This
> > means that when open-iscsi connects to these three targets, they each
> > get put on a different SCSI bus.  Any way to force all three targets
> > onto the same bus?
> Nope. Each of the connection is considered as a new HBA.

Bummer...this may make this an unusable setup for me :-(.

> > 2) open-iscsi starts ID numbering at 0.  Is there any way to configure
> > an iSCSI target to show up at a certain ID?  So, my tape library is
> > SCSI ID 8, my first drive is 9, and my second drive is 10.  Is there
> > any way to configure these targets to show up at IDs 8, 9, and 10?
> When you say ID, do you mean LUN?  What does 'lsscsi' show?
> Is your first drive the second target? If that is the case, it should
> show up as so (with a different vendor/product name of course):
> [0:0:0:8]    tape       blah      blah                                  
> /dev/st0
> [1:0:0:9]    disk    ATA      WDC WD1600JD-75H 08.0  /dev/sda
> [2:0:0:10]   disk    ATA      ST3160812AS      3.AD  /dev/sdb
> But the last digit ought to be the same as your SCSI ID, unless the
> target decided to "flatten" this an opt to present them as 1-to-1 mapping
> (one target == one LUN).

Here's the output:
[EMAIL PROTECTED] ~]# lsscsi
[20:0:0:0]   tape    SEAGATE  ULTRIUM06242-XXX 1613  /dev/st0
[21:0:0:0]   mediumx STK      L20              0215  /dev/sch0
[22:0:0:0]   tape    SEAGATE  ULTRIUM06242-XXX 1613  /dev/st1

As you can see, it does not maintain devids but each one becomes id
0.  As a result, I get the following message when the changer loads:
ch0: type #1 (mt): 0x0+1 [medium transport]
ch0: type #2 (st): 0x3e8+20 [storage]
ch0: type #3 (ie): 0xa+0 [import/export]
ch0: type #4 (dt): 0x1f4+2 [data transfer]
ch0: dt 0x1f4: ID 9, LUN 0, Huh? device not found!
ch0: dt 0x1f5: ID 10, LUN 0, Huh? device not found!
ch0: INITIALIZE ELEMENT STATUS, may take some time ...
ch0: ... finished
ch 21:0:0:0: Attached scsi changer ch0
ch 21:0:0:0: Attached scsi generic sg2 type 8

Seems like it's pretty picky about having the right IDs.  Maybe there
are some module parameters for the ch module that would let me tell it
where to try to find the drives?

You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi

Reply via email to