Re: open-iscsi, Debian Etch and network disconnections
On 26 sep, 20:06, [EMAIL PROTECTED] wrote: I do not think this is enough info. Do you just see the above then see write errors on the FS? Or do you see a error message about the other path failing? First I get a network disconnection (this is the source of all my problems I think), then I get the multipath message (it's in round- robin, so it's switching to use only one NIC) and then the writes error. Then I stopped the test because the other NIC would go down as well and, at least with 2.6.18, there were the risk of a kernel panic if writing on a remote volume without a network connection. The above errors are expected and ok because of the nic port going up and down, and they only indicate that on one path we got errors and that multipath handled it by failing a path. Exactly :) But the problem is that the network is going up and down.. it isn't supposed to act like this... I'm just testing the remote storage speed with tiobench, not disconnecting the cable to test how multipath handles failures. So I was asking for advice because I don't know if the problem is on the Linux side or on the Infortrend side (as said, they are directly connected, no switches at all between the two) If you run iscsiadm -m session -P 3 Here it is (sorry for the word wrap) logs1:~# iscsiadm -m session - P Target: iqn. 2002-10.com.infortrend:raid.sn7612961.012 Current Portal: 172.16.10.10:3260,1 Persistent Portal: 172.16.10.10:3260,1 ** Interface: ** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.1993-08.org.debian: 01.5133b441938d Iface IPaddress: 172.16.10.1 Iface HWaddress: default Iface Netdev: default SID: 1 iSCSI Connection State: LOGGED IN iSCSI Session State: Unknown Internal iscsid Session State: NO CHANGE Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 65536 MaxXmitDataSegmentLength: 65536 FirstBurstLength: 65536 MaxBurstLength: 262144 ImmediateData: Yes InitialR2T: No MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 1 State: running scsi1 Channel 00 Id 0 Lun: 0 Attached scsi disk sdb State: running scsi1 Channel 00 Id 0 Lun: 1 Attached scsi disk sdc State: running Target: iqn. 2002-10.com.infortrend:raid.sn7612996.001 Current Portal: 172.16.0.10:3260,1 Persistent Portal: 172.16.0.10:3260,1 ** Interface: ** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.1993-08.org.debian: 01.5133b441938d Iface IPaddress: 172.16.0.1 Iface HWaddress: default Iface Netdev: default SID: 2 iSCSI Connection State: LOGGED IN iSCSI Session State: Unknown Internal iscsid Session State: NO CHANGE Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 65536 MaxXmitDataSegmentLength: 65536 FirstBurstLength: 65536 MaxBurstLength: 262144 ImmediateData: Yes InitialR2T: No MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 2 State: running scsi2 Channel 00 Id 0 Lun: 0 Attached scsi disk sdd State: running scsi2 Channel 00 Id 0 Lun: 1 Attached scsi disk sde State: running You should see at least two sessions. One session would have sdb and the other session should have some other sdX that we did not see errors for in the log snippets. Exactly.. but as I said sdd will fail the same, I just stopped the test before because I don't have physical access to the machine and a reboot could be a PITA :) If you run multipath -ll mpath0 (3600d02300413075089029900) dm-0 IFT,S16E-R1130 [size=781G][features=0][hwhandler=0] \_ round-robin 0 [prio=1][enabled] \_ 1:0:0:0 sdb 8:16 [active][ready] \_ round-robin 0 [prio=1][active] \_ 2:0:0:0 sdd 8:48 [active][ready Also Konrads suggestion to use 'queue_if_no_path' or no_path_retry would fix the problem where if all paths are
Debian etch, bnx2i. Trouble getting it to work
Hi I am trying to use the bnx2i for connecting to a dell iscsi box. What I have done is upgrading the kernel to 2.4.24 ubuntu based kernel(ubuntu because they had xen patches) I have the driverpackage for bnx2i from dell and then I compiled and installed the bnx2(including cnic) and bnx2i from that driverpackage. I now modprobe bnx2i without any errors. I then found out that I needed some newer userspace utilities for setting the transport.name so I got the open-iscsi source from git, and then ran make make install_usr(because if I had installed the kernel modules from the git version I would have some problems compiling bnx2i against its header files, because it will compile against my kernelsource) Now I removed the bnx2i module from kernel;started bnx2id;modprobe bnx2i;started iscsid; then I did: iscsiadm --mode node --targetname targetname --portal portal ip -- op=update --name=node.transport_name --value=bcm570x-04 bcm570x-04 is mapped to the interface where the portal ip can be reached I then get: iscsid: Could not fund uspace transport for bcm570x-04 in daemon.log I have successfully used some disk from the dell iscsi without bnx2i, but I would like to use bnx2i if I can make it work Another thing is that eth0 which is bcm570x-04 is an interface with vlan on it - and it is that vlan which has access to the dell iscsi Best Regards Hasse H. Johansen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Specify SCSI ID
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. 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]diskATA WDC WD1600JD-75H 08.0 /dev/sda [2:0:0:10] diskATA 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). --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Specify SCSI ID
On Sep 28, 8:58 am, Nick [EMAIL PROTECTED] 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? 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? Are you familar with udev? Each target has a unique name right? Since each target has one device, you could write a udev rule that grabs the target name and for target X creates a special /dev/my_device_name for the tape device accessed through it. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: OpenSuse 10sp3 conn error
On Sep 27, 9:26 am, iscsiFans [EMAIL PROTECTED] wrote: Hi,all, I have install Opensuse 10sp3 (x86_64)+ Open-iscsi 2.865(iscsid) + Multipath-tools-0.4.7-80, Config and login is ok but I find /var/log/ messages have many conne error, so multipath is change-link many times, sometime when conn error, the server is hang, such as: iscsid v2.0.866 Sep 26 11:49:34 linux-j2cx iscsid: can not send nopin response I try to change the noop_timeout parameter, But it's no use: I do not think changing that value will help in this case, because above the target is sending us a nop and we are trying to respond to it. For some reason we are failing on sending a response the targets nop. What target are you using btw? If you could run iscsid by hand with debugging by doing # iscsid -d 8 -f we can see why it is failing. You might need to stop the iscsi service, then run # iscsiad -d 8 -f # iscsiadm -m node -L automatic or instead of the last command you can log into a specific target by doing iscsiadm -m node -T target -p ip -l Send all the out put from the iscsid. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: iSNS not broadcasting a new target
On Sep 29, 11:59 am, [EMAIL PROTECTED] wrote: its client interacts with open-iscsi. For upstream we are still waiting to hook into open-isns (the oracle one) or linux-isns (it still needs a lib last I looked) to really do isns properly. Sorry to go offtopic, but if open solaris had a good isns library that initiators can hook into I would not be against using that. If you guys are interested let me know. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Debian etch, bnx2i. Trouble getting it to work
Hi Anil Thanks for your answer. I am using debian etch, but with kernelsource from ubuntu(That is because I had problems compiling bnx2i against a newer open-iscsi because bnx2i would compile againt my kernel headers(2.6.18 from debian etch which has broken iscsi) which is the wrong headers because it is from an old version) The version is 2.6.24.3 Do I need newer iscsi kernel modules than what 2.6.14.3 provides for using bnx2i ? And if I need that How can I get the bnx2i driver to compile againt the headers etc. from openiscsi instead of the kernelsource? I should metion that I get the: iscsid: Could not fund uspace transport for bcm570x-04 when I do iscsiadm --mode node --targetname target --portal portal ip -- login and along with that iscsiadm says: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) This makes me believe that maybe my kernel modules(from the 2.6.24.3 kernel) is missing some features? Best Regards Hasse On Sep 29, 5:32 pm, Anil Veerabhadrappa [EMAIL PROTECTED] wrote: Hasse, We will look into this and get back with a definitive answer soon. Can you exactly tell me what Ubuntu release distribution you are using? - Anil Veerabhadrappa From: open-iscsi@googlegroups.com [EMAIL PROTECTED] On Behalf Of Alfafa [EMAIL PROTECTED] Sent: Monday, September 29, 2008 2:03 AM To: open-iscsi Cc: [EMAIL PROTECTED] Subject: Debian etch, bnx2i. Trouble getting it to work Hi I am trying to use the bnx2i for connecting to a dell iscsi box. What I have done is upgrading the kernel to 2.4.24 ubuntu based kernel(ubuntu because they had xen patches) I have the driverpackage for bnx2i from dell and then I compiled and installed the bnx2(including cnic) and bnx2i from that driverpackage. I now modprobe bnx2i without any errors. I then found out that I needed some newer userspace utilities for setting the transport.name so I got the open-iscsi source from git, and then ran make make install_usr(because if I had installed the kernel modules from the git version I would have some problems compiling bnx2i against its header files, because it will compile against my kernelsource) Now I removed the bnx2i module from kernel;started bnx2id;modprobe bnx2i;started iscsid; then I did: iscsiadm --mode node --targetname targetname --portal portal ip -- op=update --name=node.transport_name --value=bcm570x-04 bcm570x-04 is mapped to the interface where the portal ip can be reached I then get: iscsid: Could not fund uspace transport for bcm570x-04 in daemon.log I have successfully used some disk from the dell iscsi without bnx2i, but I would like to use bnx2i if I can make it work Another thing is that eth0 which is bcm570x-04 is an interface with vlan on it - and it is that vlan which has access to the dell iscsi Best Regards Hasse H. Johansen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Debian etch, bnx2i. Trouble getting it to work
Hi Anil Thanks for your answer. I am using debian etch, but with kernelsource from ubuntu(That is because I had problems compiling bnx2i against a newer open-iscsi because bnx2i would compile againt my kernel headers(2.6.18 from debian etch which has broken iscsi) which is the wrong headers because it is from an old version) The version is 2.6.24.3 Do I need newer iscsi kernel modules than what 2.6.14.3 provides for using bnx2i ? And if I need that How can I get the bnx2i driver to compile againt the headers etc. from openiscsi instead of the kernelsource? I should metion that I get the: iscsid: Could not fund uspace transport for bcm570x-04 when I do iscsiadm --mode node --targetname target --portal portal ip -- login and along with that iscsiadm says: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) This makes me believe that maybe my kernel modules(from the 2.6.24.3 kernel) is missing some features? Best Regards Hasse On Sep 29, 5:32 pm, Anil Veerabhadrappa [EMAIL PROTECTED] wrote: Hasse, We will look into this and get back with a definitive answer soon. Can you exactly tell me what Ubuntu release distribution you are using? - Anil Veerabhadrappa From: open-iscsi@googlegroups.com [EMAIL PROTECTED] On Behalf Of Alfafa [EMAIL PROTECTED] Sent: Monday, September 29, 2008 2:03 AM To: open-iscsi Cc: [EMAIL PROTECTED] Subject: Debian etch, bnx2i. Trouble getting it to work Hi I am trying to use the bnx2i for connecting to a dell iscsi box. What I have done is upgrading the kernel to 2.4.24 ubuntu based kernel(ubuntu because they had xen patches) I have the driverpackage for bnx2i from dell and then I compiled and installed the bnx2(including cnic) and bnx2i from that driverpackage. I now modprobe bnx2i without any errors. I then found out that I needed some newer userspace utilities for setting the transport.name so I got the open-iscsi source from git, and then ran make make install_usr(because if I had installed the kernel modules from the git version I would have some problems compiling bnx2i against its header files, because it will compile against my kernelsource) Now I removed the bnx2i module from kernel;started bnx2id;modprobe bnx2i;started iscsid; then I did: iscsiadm --mode node --targetname targetname --portal portal ip -- op=update --name=node.transport_name --value=bcm570x-04 bcm570x-04 is mapped to the interface where the portal ip can be reached I then get: iscsid: Could not fund uspace transport for bcm570x-04 in daemon.log I have successfully used some disk from the dell iscsi without bnx2i, but I would like to use bnx2i if I can make it work Another thing is that eth0 which is bcm570x-04 is an interface with vlan on it - and it is that vlan which has access to the dell iscsi Best Regards Hasse H. Johansen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: iSNS not broadcasting a new target
On Sep 29, 2008, at 11:02 AM, [EMAIL PROTECTED] wrote: On Sep 29, 11:59 am, [EMAIL PROTECTED] wrote: its client interacts with open-iscsi. For upstream we are still waiting to hook into open-isns (the oracle one) or linux-isns (it still needs a lib last I looked) to really do isns properly. Sorry to go offtopic, but if open solaris had a good isns library that initiators can hook into I would not be against using that. If you guys are interested let me know. I don't really work too much with this; I will find out who does, and get back to you. Best /jb --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: iSNS not broadcasting a new target
On Sep 29, 2008, at 10:59 AM, [EMAIL PROTECTED] wrote: On Sep 28, 11:00 pm, Jesse Butler [EMAIL PROTECTED] wrote: Given the below software revs, we're seeing an issue wherein when a new target is added, the iSNS server picks it up, but logged in initiators do not see it. I am not an iSNS expert, but apparently a few snoops were done and the iSNS server is not sending out the proper message indicating a new target being available. Is there a known bug around this? Thanks Jesse Kernel version: Linux frederic-ar 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux OpeniSCSI version: frederic-ar:~ # rpm -qi open-iscsi-2.0.707-0.19 Name: open-iscsi Relocations: (not relocatable) Version : 2.0.707 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 0.19 Build Date: Mon May 14 08:08:37 2007 Install Date: Tue Aug 12 05:14:39 2008 Build Host: nepomuk.suse.de Group : Productivity/Networking/Other Source RPM: open- iscsi-2.0.707-0.19.src.rpm Size: 463279 License: GNU General Public License (GPL) Signature : DSA/SHA1, Mon May 14 08:13:50 2007, Key ID a84edae89c800aca Packager:http://bugs.opensuse.org URL :http://www.open-iscsi.org Summary : Linux* Open-iSCSI Software Initiator iSNS server : frederic-ar:~ # rpm -qi isns-2.0.05-0.5 Name: isns Relocations: (not relocatable) Version : 2.0.05Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 0.5 Build Date: Thu May 3 07:27:57 2007 Install Date: Wed Aug 6 21:58:39 2008 Build Host: lanner.suse.de Group : System/DaemonsSource RPM: isns-2.0.05-0.5.src.rpm Size: 345497 License: BSD License and BSD-like Signature : DSA/SHA1, Thu May 3 07:30:53 2007, Key ID a84edae89c800aca Packager:http://bugs.opensuse.org URL :http://sourceforge.net/projects/linuxisns/ Summary : Internet Storage Naming Service I have not seen this reported to the lists. The open-iscsi isns code only handles discovery. I am not sure what the suse code does or how its client interacts with open-iscsi. For upstream we are still waiting to hook into open-isns (the oracle one) or linux-isns (it still needs a lib last I looked) to really do isns properly. Ok, so the idea of an initiator seeing a new target automagically at this point is a future feature? Just want to make sure we're not missing anything. It might be be faster to make a suse bugzilla, because I do not think the suse and novell isns guys follow the list closely. Ok, thanks. Best /jb --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Specify SCSI ID
On Sep 29, 10:29 am, [EMAIL PROTECTED] wrote: On Sep 28, 8:58 am, Nick [EMAIL PROTECTED] 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? 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? Are you familar with udev? Each target has a unique name right? Since each target has one device, you could write a udev rule that grabs the target name and for target X creates a special /dev/my_device_name for the tape device accessed through it. But the changer doesn't work by device names, it works by device IDs. This is the message I get 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 As you can see, it's looking for specific SCSI IDs, probably on the same SCSI bus, to try to find the tape devices. -Nick --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Specify SCSI ID
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] tapeSEAGATE ULTRIUM06242-XXX 1613 /dev/st0 [21:0:0:0] mediumx STK L20 0215 /dev/sch0 [22:0:0:0] tapeSEAGATE 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? -Nick --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Specify SCSI ID
Those look helpful, but the issue is that these seem to only take a single id and lun and don't let you specify the host bus on which these devices are located. I suppose I could try presenting them on the same ID (same iSCSI Target) with different LUNs, then all I'd have to do is set dt_id to 0 and use the two LUNs. Worth a shot, I guess... -Nick On Sep 29, 3:49 pm, Konrad Rzeszutek [EMAIL PROTECTED] wrote: 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: Yeah, this is the fault of your storage. It converst the SCSI Ids in each seperate target. 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? Try 'modinfo ch'. The 'dt_id' and 'dt_lun' looks promising. -Nick --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Specify SCSI ID
On Sep 29, 3:49 pm, Konrad Rzeszutek [EMAIL PROTECTED] wrote: 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: Yeah, this is the fault of your storage. It converst the SCSI Ids in each seperate target. I'm not sure what you mean by this being a fault of my storage. It is normal for libraries and tape drives to have different SCSI IDs. I'm using SCST for the iSCSI Target Server, and that either allows me to specify all of the SCSI devices under the same target as different LUNs, or specify them under different targets. SCST does not allow me to specify the ID the devices are presented as - maybe that's the fault to which you're referring? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: iSNS not broadcasting a new target
On Sep 29, 2008, at 1:55 PM, Jesse Butler wrote: On Sep 29, 2008, at 11:02 AM, [EMAIL PROTECTED] wrote: On Sep 29, 11:59 am, [EMAIL PROTECTED] wrote: its client interacts with open-iscsi. For upstream we are still waiting to hook into open-isns (the oracle one) or linux-isns (it still needs a lib last I looked) to really do isns properly. Sorry to go offtopic, but if open solaris had a good isns library that initiators can hook into I would not be against using that. If you guys are interested let me know. Solaris does not have any sort of iSNS library. We have initiator and server code, and there is not much in common between the two, so the idea of implementing a library was not really vetted. Best Jesse --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
