4:39 a.m.
I did the following right now to be sure:
- rotated logs
- deleted the LUN from Storage and created new one (so LUN is unused)
- rebooted the server
- opened oVirt Engine Web Administration
- Storage -> New Domain
- checked my newly created LUN
--> Error
- pressed button "OK" one more time - Another Error
I have no other iSCSI storage domains on my installaion. I tried to create another LUN on
SAN with smaller size, but result is the same.
Thanks in advance. I hope this information will help to find out what's wrong...
----- Original Message -----
We would also like to know whether the first creation of the iscsi
storage domain succeeded and only the latter ones failed.
Whether you possibly tried to create a storage domain with a already used lun, and
specifically - do you have any iscsi storage domain at all that you can see on the
webadmin?
Regards,
Vered
----- Original Message -----
> From: "Eduardo Warszawski" <ewarszaw(a)redhat.com>
> To: "Vered Volansky" <vered(a)redhat.com>
> Cc: users(a)ovirt.org
> Sent: Thursday, February 21, 2013 11:57:09 AM
> Subject: Re: [Users] HELP! Errors creating iSCSI Storage Domain
>
>
>
> ----- Original Message -----
>> Hi,
>>
>> Please add engine and vdsm full logs.
>>
>> Regards,
>> Vered
>>
>> ----- Original Message -----
>>> From: "Кочанов Иван" <kia(a)dcak.ru>
>>> To: users(a)ovirt.org
>>> Sent: Thursday, February 21, 2013 4:26:14 AM
>>> Subject: [Users] HELP! Errors creating iSCSI Storage Domain
>>>
>>>
>>> LUN info:
>>> # iscsiadm -m discovery -t st -p 172.16.20.1
>>> 172.16.20.1:3260,1
>>> iqn.2003-10.com.lefthandnetworks:mg-dcak-p4000:134:vol-os-virtualimages
>>>
>>> # pvs
>>> PV VG Fmt Attr PSize PFree
>>> /dev/mapper/36000eb35f449ac1c0000000000000086
>>> db260c45-8dd2-4397-a5bf-fd577bbbe0d4 lvm2 a-- 1023.62g 1023.62g
>>>
> The PV already belongs to VG db260c45-8dd2-4397-a5bf-fd577bbbe0d4.
> This VG was very probably created by ovirt and is part of a
> StorageDomain.
> (Then you already succeeded.)
> If you are sure that no valuable info is in this VG you can use the
> "force" thick.
> Anyway I suggest you to look for the SDUUID:
> db260c45-8dd2-4397-a5bf-fd577bbbe0d4
> and removing this StorageDomain from the system or use this already
> created SD.
>
> vdsm and engine logs will be very valuable, as Vered said.
> Please include them since you started, in order to confirm to which
> SD the lun belongs.
>
> Best regards,
> E.
>
>>>
>>>
>>> --
>>> Sysadmin DCAK kia(a)dcak.ru
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users