Hi! Ahaa, I can shed some light here... This is a part of the log in engine: 2012-07-15 13:46:51,837 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http--0.0.0.0-8080-3) Vds: node1.hemma.home 2012-07-15 13:46:51,837 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (http--0.0.0.0-8080-3) Command CreateVGVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to CreateVGVDS, error = Volume Group not big enough: ('VG size must be more than 10240 MiB',) 2012-07-15 13:46:51,837 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVGVDSCommand] (http--0.0.0.0-8080-3) FINISH, CreateVGVDSCommand, log id: da915ec 2012-07-15 13:46:51,838 ERROR [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to CreateVGVDS, error = Volume Group not big enough: ('VG size must be more than 10240 MiB',) 2012-07-15 13:46:51,859 INFO  [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command [id=db9901fd-9f2d-4298-88d9-70dd898fa4bd]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage_domain_dynamic; snapshot: ae76ccdb-e920-436c-b623-09d5e3db3acd. 2012-07-15 13:46:51,869 INFO  [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command [id=db9901fd-9f2d-4298-88d9-70dd898fa4bd]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage_domain_static; snapshot: ae76ccdb-e920-436c-b623-09d5e3db3acd. 2012-07-15 13:46:51,890 ERROR [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Transaction rolled-back for command: org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand. 2012-07-15 13:46:52,049 WARN  [org.ovirt.engine.core.bll.storage.AttachStorageDomainToPoolCommand] (http--0.0.0.0-8080-3) CanDoAction of action AttachStorageDomainToPool failed. Reasons:VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_NOT_EXIST And the important part is that it say`s that "error = Volume Group not big enough: ('VG size must be more than 10240 MiB',)" The LUN I created is a qcow2-LUN of 50 Gb size, which of coarse doesn't have the size of 50 Gb, because it is a thin provisioned LUN. So question is then: Doesn't oVirt support thin provisioned LUN's? If not, it is not very good, because most SAN's provide thin provisioned LUN's nowaday's...

This is perhaps a limitation of LVM2? It would be a real setback to not be able to use qcow2, though.... Regards Johan -----Jakub Libosvar <libosvar(a)redhat.com&gt; skrev: ----- Till: Johan Kragsterman <johan.kragsterman(a)capvert.se&gt; Från: Jakub Libosvar <libosvar(a)redhat.com&gt; Datum: 2012.07.20 10:37 Ärende: Re: [Users] "Error: Cannot attach Storage. Storage Domain doesn't exist." On 07/20/2012 10:27 AM, Johan Kragsterman wrote: > Thanks for you respons, Kuba! > > But I didn't attach any log, I was refering to the log attached by Trey Dockendorf in his post: "iSCSI discovery not showing all LUNs - oVirt 3.1", where he is describing an error with the same message as in my post. > >    I don't have a log, since I run only a small hypervisor and haven't enabled external logging... There should be logging by default, you can find it at /var/log/vdsm/vdsm.log on your hypervisor. >    Or is there logging on the engine as well, in this matter...? On machine where oVirt is installed you can find one in /var/log/ovirt-engine/engine.log Kuba > Rgrds Johan > > -----users-bounces(a)ovirt.org skrev: ----- > Till: Johan Kragsterman <johan.kragsterman(a)capvert.se&gt; > Från: Jakub Libosvar > Sänt av: users-bounces(a)ovirt.org > Datum: 2012.07.20 10:17 > Kopia: users(a)ovirt.org > Ärende: Re: [Users] "Error: Cannot attach Storage. Storage Domain doesn't exist." > > On 07/19/2012 07:35 PM, Johan Kragsterman wrote: >>     Hi all! >> >> This is my first post to this list. >> >> I set up a fedora16 HV, and an oVirt engine on fedora 16, both booted and installed on fibre channel storage. >> >> Everything works fine, shows up in web gui on engine, host discovered and active, until that I try to attach storage. >> >> Then I get this message: "Error: Cannot attach Storage. Storage Domain doesn't exist." >> >>     Same as in the post: "iSCSI discovery not showing all LUNs - oVirt 3.14", also this month. >> >> In that post discuss if LUN's are dirty or not. My LUN's are not dirty. >> >> I checked that by removing the data LUN, removing the LUN mapping creating a new LUN I didn't use(so the new LUN I will use didn't use something of the old one), and finally creating a new LUN of different size. >> >>     Same result with that LUN when I try to use it as storage domain: "Error: Cannot attach Storage. Storage Domain doesn't exist." >> >>     I was reading the enclosed vdsm-log of the message: "iSCSI discovery not showing all LUNs - oVirt 3.14" > Hi Johan, > > could you please try to attach the vdsm log again? I don't have it > attached in this mail. > > Thanks, > Kuba >>     The log was a lot about MPIO, if I understood right. Could it be that the MPIO driver isn't discover a dual path, only a single path? Right now I don't have an fc switch, so I am unable to test if that would solve the problem. >> >> Anyone have any suggestions? >> >> Regards Johan >> _______________________________________________ >> 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