[ovirt-users] Issues with Storage domain

Carlos A. Diaz carlos_d99 at yahoo.com
Mon Sep 8 17:07:27 UTC 2014


I think it is related to the Domain ID, attached you will find a snippet of the vdsm logs on the SPM host.

Carlos


On Monday, September 8, 2014 11:58 AM, Carlos A. Diaz <carlos_d99 at yahoo.com> wrote:
 


Thanks Nir,

Attached is a Snippet of the log, that essentially keeps going and going with a few alerts of the engine trying to migrate some VMs unsuccessfully which is pretty much related to the fact that the storage is not available; so I filtered those out.

Does storageDomainId = 00000000-0000-0000-0000-000000000000 sounds right?

Anyways, I am looking at older logs to see if the domain ID changed, I will keep you posted, if you need anything else let me know, and thanks again :)

Carlos


On Sunday, September 7, 2014 7:26 PM, Nir Soffer <nsoffer at redhat.com> wrote:
 


----- Original Message -----
> From: "Carlos A. Diaz" <carlos_d99 at yahoo.com>
> To: users at ovirt.org
> Sent: Friday, September 5, 2014 9:36:42 PM
> Subject: [ovirt-users] Issues with Storage domain
> 
> Hello everyone, its my first time here; so I hope I am on the
 right place
> 
> I had a problem where one of our SysAdmins cloned our NFS production export
> in order to create a new NFS export, but he didn't changed the FSID, so we
> ended up with 2 nfs exports using the same ID. I was able to roll back and
> recover the data, once I had corrected everything I went to the hosts and
> unpaused the VMs from the CLI (I lost the engine in the process), so now we
> are back up and running.
> 
> My problem right now is that oVirt says that our main storage domain is
> "Down" and I can't bring it up, so essentially I cannot start any VMs on
> that domain, which hosts 90% of our production environment; which is also
> scary because I am not sure how to recover from this error without affecting
> my production environment.
> 
> My guess is that at some point the MD5 hash changed, or something in the
> metadata for that Domain, but I don't know if this is the problem and if
> recreating the signature is possible without breaking my existing
> configuration.
> 
> Is there anyway to mark it as UP from the database or at any other level
> without breaking (more) the config?

Hi Carlos,

Please attach engine.log and vdsm.log, hopefully we can understand from
the logs why you cannot activate the storage domain.


Thanks,
Nir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140908/6f596dfe/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vdsm
Type: application/octet-stream
Size: 9512 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140908/6f596dfe/attachment-0001.obj>


More information about the Users mailing list