9:22 a.m.
I did following steps:
- delete target on all initiators (ovirt nodes)
iscsiadm -m node -T iqn.2017-03.cz.dragon.ovirt.fuvs-sn1:10T -p
10.53.1.201:3260 -u
iscsiadm -m node -T iqn.2017-03.cz.dragon.ovirt.fuvs-sn1:10T -p
10.53.1.201:3260 -o delete
- stop tgtd on target
- fill storage by zeroes (dd if=/dev/zero of=/dev/md125 bs=4096
status=progress)
- start tgtd
- tried to connect to ovirt (Discovery=ok, Login=ok, but can not see any
LUN).
=== After that I ran this commands on one node: ===
[root@fudi-cn1 ~]# iscsiadm -m session -o show
tcp: [1] 10.53.0.10:3260,1 iqn.2017-03.cz.dragon.ovirt:ovirtengine
(non-flash)
tcp: [11] 10.53.0.201:3260,1 iqn.2017-03.cz.dragon.ovirt.fudi-sn1:10T
(non-flash)
tcp: [12] 10.53.1.201:3260,1 iqn.2017-03.cz.dragon.ovirt.fuvs-sn1:10T
(non-flash)
[root@fudi-cn1 ~]# iscsiadm -m discoverydb -P1
SENDTARGETS:
DiscoveryAddress: 10.53.0.201,3260
Target: iqn.2017-03.cz.dragon.ovirt:ovirtengine
Portal: 10.53.0.201:3260,1
Iface Name: default
iSNS:
No targets found.
STATIC:
Target: iqn.2017-03.cz.dragon.ovirt.fuvs-sn1:10T
Portal: 10.53.1.201:3260,1
Iface Name: default
Target: iqn.2017-03.cz.dragon.ovirt:ovirtengine
Portal: 10.53.0.10:3260,1
Iface Name: default
Target: iqn.2017-03.cz.dragon.ovirt.fudi-sn1:10T
Portal: 10.53.0.201:3260,1
Iface Name: default
FIRMWARE:
No targets found.
=== On iscsi target: ===
[root@fuvs-sn1 ~]# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md125 : active raid6 sdl1[11] sdk1[10] sdj1[9] sdi1[8] sdh1[7] sdg1[6]
sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0]
9766302720 blocks super 1.2 level 6, 512k chunk, algorithm 2 [12/12]
[UUUUUUUUUUUU]
bitmap: 0/8 pages [0KB], 65536KB chunk
...etc...
[root@fuvs-sn1 ~]# cat /etc/tgt/targets.conf
default-driver iscsi
<target iqn.2017-03.cz.dragon.ovirt.fuvs-sn1:10T>
# provided devicce as a iSCSI target
backing-store /dev/md125
# iSCSI Initiator's IP address you allow to connect
#initiator-address 10.53.0.0/23
</target>
--
Lukas Kaplan
2017-03-25 12:36 GMT+01:00 Lukas Kaplan <lkaplan(a)dragon.cz>:
Co muze myslet tim mappingem?
Jinak muzu zkusit ddckem celou storage prepsat nulami.
co ty na to?
Odesláno z iPhonu
Začátek přeposílané zprávy:
*Od:* Yaniv Kaul <ykaul(a)redhat.com>
*Datum:* 24. března 2017 23:25:21 SEČ
*Komu:* Lukáš Kaplan <lkaplan(a)dragon.cz>
*Kopie:* users <users(a)ovirt.org>
*Předmět:* *Re: [ovirt-users] iSCSI Discovery cannot detetect LUN*
On Fri, Mar 24, 2017 at 1:34 PM, Lukáš Kaplan <lkaplan(a)dragon.cz> wrote:
> Hello all,
>
> please do you have some experience with troubleshooting adding of iSCSI
> domain to ovirt 4.1.1?
>
> I am chalenging this issue now:
>
> 1) I have successfuly installed oVirt 4.1.1 environment with self-hosted
> engine, 3 nodes and 3 storages (iSCSI Master domain, iSCSI for hosted
> engine and NFS ISO domain). Everything is working now.
>
> 2) But, when I want to add new iSCSI domain, I can discover it, I can
> login, but I cant see any LUN on that storage. (I had same problem in oVirt
> 4.1.0, so I made upgrade to 4.1.1)
>
Are you sure mappings are correct?
Can you ensure the LUN is empty?
Y.
>
> 3) Then I tryed to add this storage to another oVirt environment (oVirt
> 3.6) and there are no problem. I can see LUN on that storage and I can
> connect it to oVirt.
>
> I tryed to examine vdsm.log, but it is very detailed and unredable for me
> :-/
>
> Thak you in advance, have a nice day,
> --
> Lukas Kaplan
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>