Hello, I have a CentOS 6.5 server offering iscsi luns via scsi-target-utils. Lun 1 is configured as a storage domain in oVirt. Now I add a second lun on server but it seems oVirt is not able to discovery it.. Am I missing anyting simple? On the server offering iSCSI target: # tgtadm --lld iscsi --mode target --op show Target 1: iqn.2014-07.local.localdomain:store1 System information: Driver: iscsi State: ready I_T nexus information: I_T nexus: 1 Initiator: iqn.1994-05.com.redhat:5d9b31319a8e Connection: 0 IP Address: 10.10.1.61 LUN information: LUN: 0 Type: controller SCSI ID: IET 00010000 SCSI SN: beaf10 Size: 0 MB, Block size: 1 Online: Yes Removable media: No Prevent removal: No Readonly: No Backing store type: null Backing store path: None Backing store flags: LUN: 1 Type: disk SCSI ID: p_iscsi_store1_l SCSI SN: 66666a41 Size: 214738 MB, Block size: 512 Online: Yes Removable media: No Prevent removal: No Readonly: No Backing store type: rdwr Backing store path: /dev/drbd/by-res/iscsiha Backing store flags: LUN: 2 Type: disk SCSI ID: p_iscsi_store1_l SCSI SN: 12267514 Size: 536850 MB, Block size: 512 Online: Yes Removable media: No Prevent removal: No Readonly: No Backing store type: rdwr Backing store path: /dev/drbd/by-res/iscsiesx Backing store flags: Account information: iscsiuser ACL information: 10.10.1.61 10.10.1.62 10.10.1.63 PS: both luns are drbd volumes and the server is master for both... ... 2: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----- ns:3124 nr:116228 dw:119352 dr:31816 al:23 bm:14 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0 3: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----- ns:0 nr:0 dw:0 dr:680 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0 Lun 1 is already what previously discovered and connected, but I'm not able to see the new lun, only the old one that is grayed out (because already connected). Tried both strategies to edit the existing SD and o add a new SD (is it possible to add a new SD pointing to the same ip target and connecting new luns?) Thanks in advance, Gianluca
Once upon a time, Gianluca Cecchi <gianluca.cecchi@gmail.com> said:
Am I missing anyting simple?
Yep...
On the server offering iSCSI target: # tgtadm --lld iscsi --mode target --op show Target 1: iqn.2014-07.local.localdomain:store1 LUN: 1 SCSI ID: p_iscsi_store1_l LUN: 2 SCSI ID: p_iscsi_store1_l
Both LUNs have the same ID name, which confuses discovery (I've done the same thing before). This is a 16 character string, so make sure they are distinct/unique in that 16 characters. It is annoying that scsi-target-utils lets you do this. -- Chris Adams <cma@cmadams.net>
On Mon, Dec 1, 2014 at 5:26 PM, Chris Adams <cma@cmadams.net> wrote:
Once upon a time, Gianluca Cecchi <gianluca.cecchi@gmail.com> said:
Am I missing anyting simple?
Yep...
On the server offering iSCSI target: # tgtadm --lld iscsi --mode target --op show Target 1: iqn.2014-07.local.localdomain:store1 LUN: 1 SCSI ID: p_iscsi_store1_l LUN: 2 SCSI ID: p_iscsi_store1_l
Both LUNs have the same ID name, which confuses discovery (I've done the same thing before). This is a 16 character string, so make sure they are distinct/unique in that 16 characters.
It is annoying that scsi-target-utils lets you do this. -- Chris Adams <cma@cmadams.net> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Arghhh! Actually the name I used is p_iscsi_store1_lun1 p_iscsi_store1_lun2 and the problem so should be that it is trimmed to 16 chars... I will try Thanks!!
On Mon, Dec 1, 2014 at 5:30 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Mon, Dec 1, 2014 at 5:26 PM, Chris Adams <cma@cmadams.net> wrote:
Once upon a time, Gianluca Cecchi <gianluca.cecchi@gmail.com> said:
Am I missing anyting simple?
Yep...
On the server offering iSCSI target: # tgtadm --lld iscsi --mode target --op show Target 1: iqn.2014-07.local.localdomain:store1 LUN: 1 SCSI ID: p_iscsi_store1_l LUN: 2 SCSI ID: p_iscsi_store1_l
Both LUNs have the same ID name, which confuses discovery (I've done the same thing before). This is a 16 character string, so make sure they are distinct/unique in that 16 characters.
It is annoying that scsi-target-utils lets you do this. -- Chris Adams <cma@cmadams.net> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Arghhh! Actually the name I used is p_iscsi_store1_lun1 p_iscsi_store1_lun2
and the problem so should be that it is trimmed to 16 chars... I will try
Thanks!!
The original problem actually was to configure a new iSCSI lun for VMware on the same store provided by scsi-target-utils and this new lun was not visible... So I tried originating with oVirt to crosscheck.... Now, after changing the ID, I have # tgtadm --lld iscsi --mode target --op show | grep "SCSI ID" SCSI ID: IET 00010000 SCSI ID: p_iscsi_store1_l SCSI ID: p_lun2_istore1 and the result is that VMware is able to see the new lun ;-) But the same didn't originate any change at oVirt side: the discovery, with and without chap selected (see this thread that should be solved in my version that is 3.5: http://lists.ovirt.org/pipermail/users/2014-September/027388.html) doesn't show the new LUN to attach, only LUN 1... Any log or tes I can provide to debug problem of oVirt discovery? Gianluca
On 01/12/14 17:26, Chris Adams wrote:
It is annoying that scsi-target-utils lets you do this.
Maybe file a bug to solve this? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
participants (3)
-
Chris Adams -
Gianluca Cecchi -
Sven Kieske