Hi Ian, 

I really like to understand how it happened, there are several ways to fix this 
issue,
please send us engine and vdsm logs for a start.
as for fixing the issue, we will probably have to perform some manual 
intervention on either engine data-base (preferable) or storage
metadata.
its a bit complex, and might cause other things to fail if not doing carefully, 
so its your call. 


----- Original Message -----
> From: "Ian Forde" <[email protected]>
> To: [email protected]
> Sent: Sunday, December 30, 2012 12:31:31 PM
> Subject: [Users] Fwd: Power outage = storage outage = ovirt crash with 
> mismatched master storage domain?
> 
> 
> (resend, as it might have tried to go through before my subscription
> to the list was active...)
> 
> 
> ---------- Forwarded message ----------
> From: Ian Forde < [email protected] >
> Date: Sun, Dec 30, 2012 at 1:57 AM
> Subject: Power outage = storage outage = ovirt crash with mismatched
> master storage domain?
> To: [email protected]
> 
> 
> Hi all -
> 
> 
> I'm running Ovirt from the dreyou packages (ovirt-engine 3.1.0-3.26)
> on CentOS 6.3, with 3 hypervisors all running CentOS 6.3 with
> dreyou-packaged vdsm 4.10.1-0.77.20 running. Storage is a Synology
> 1812+.
> 
> 
> And tonight I had a series of power "events" that affected the NAS.
> (So much for the small UPS. Storage has now been moved to a bigger
> UPS.) Anyway - it turns out that my storage went down 3 times while
> I was out. The NAS recovered. Ovirt didn't.
> 
> 
> I've tried putting boxes into maintenance mode. I've tried reboots
> and "confirm reboot". I've even shut everything down and brought it
> back up from scratch. What I'm facing now is a message in the GUI
> that states:
> 
> 
> "Sync Error on Master Domain between Host bv-hv01 and oVirt Engine.
> Domain BV4Pool1 is marked as Master in oVirt Engine database but not
> on the Storage side. Please consult with Support on how to fix this
> issue."
> 
> 
> Now, what was *supposed* to be my master storage domain is named
> "BV4Data-Master", and BV4Pool1 is where the VM disks are stored.
> (I'm not crazy about putting VM disks into the master pool.)
> 
> 
> So why does the database have the wrong entry and how do I fix it?
> Currently everything is *down*, given that the last time I tried to
> mess with oVirt innards I had to recreate my DC and restore all of
> the VMs by hand. Not something I'd like to do again...
> 
> 
> (This, of course, also means that I need to get proper oVirt database
> backups going...)
> 
> 
> Any ideas?
> 
> 
> -I
> 
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.ovirt.org/mailman/listinfo/users
> 
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to