[ovirt-users] storage domain don't go active anymore after 3.5.3 update
Nathanaël Blanchet
blanchet at abes.fr
Wed Jun 17 16:26:11 UTC 2015
Thank you for reply,
I found some reason to the issue : I installed a physical host through
an automated kickstart process and this host took active lun from ovirt
lun. During the install process, it created a LVM centos-home which
included this ovirt lun, but it seems that it formatted this LV in XFS.
Vms still run without issue an d we can see their LVM id in their own
host. But if one stops one vm, they can't boot anymore.
More, if I reboot a physical host, this host loses all its LVM but we
still can see the lun multipath. And instead of ovirt LVM, I see now the
centos-home LVM .... :(
So my question is :
Does it exist a tool to repair the initial ovirt lvm tags?
If I can't do such a thing, my plan is to dd the /dev/mapper/[vmdevid]
in the same time the vm is running... I would prefer to do this when the
vm is down or when I get a LVM snapshot. Do you think this to be possible?
Thank you for your help.
Le 17/06/2015 17:43, Aharon Canan a écrit :
> Hi
>
> from logs it seems like StorageDomain
> ID 229c74b0-75b0-48a5-b017-d794343b535b is missing
>
> engine -
> 2015-06-17 14:37:49,918 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand]
> (org.ovirt.thread.pool-8-thread-45) [7dc07cff] START,
> ActivateStorageDomainVDSCommand( storagePoolId =
> 1a71a643-8234-4137-800e-d7a9957857d3, ignoreFailoverLimit = false,
> storageDomainId = 229c74b0-75b0-48a5-b017-d794343b535b), log id: 72ff5345
>
> vdsm -
> Thread-80::ERROR::2015-06-17
> 15:14:17,907::domainMonitor::256::Storage.DomainMonitorThread::(_monitorDomain)
> Error while collecting domain 229c74b0-75b0-48a5-b017-d794343b535b
> monitoring information
> Traceback (most recent call last):
> File "/usr/share/vdsm/storage/domainMonitor.py", line 232, in
> _monitorDomain
> self.domain.selftest()
> File "/usr/share/vdsm/storage/sdc.py", line 49, in __getattr__
> return getattr(self.getRealDomain(), attrName)
> File "/usr/share/vdsm/storage/sdc.py", line 52, in getRealDomain
> return self._cache._realProduce(self._sdUUID)
> File "/usr/share/vdsm/storage/sdc.py", line 122, in _realProduce
> domain = self._findDomain(sdUUID)
> File "/usr/share/vdsm/storage/sdc.py", line 141, in _findDomain
> dom = findMethod(sdUUID)
> File "/usr/share/vdsm/storage/sdc.py", line 171, in _findUnfetchedDomain
> raise se.StorageDomainDoesNotExist(sdUUID)
> StorageDomainDoesNotExist: Storage domain does not exist:
> (u'229c74b0-75b0-48a5-b017-d794343b535b',)
>
>
> Can you please check if this VG
> ('229c74b0-75b0-48a5-b017-d794343b535b') exist in the host and all
> it's PVs exist as well?
> if one is missing try to check if the host can see the missing lun.
>
>
> Regards,
> __________________________________________________
> *Aharon Canan*
> int phone - 8272036
> ext phone - +97297692036
> email - acanan at redhat.com
>
> ------------------------------------------------------------------------
>
> *From: *"Nathanaël Blanchet" <blanchet at abes.fr>
> *To: *"Aharon Canan" <acanan at redhat.com>
> *Cc: *users at ovirt.org
> *Sent: *Wednesday, June 17, 2015 4:33:21 PM
> *Subject: *Re: [ovirt-users] storage domain don't go active
> anymore after 3.5.3 update
>
> Just to specify that in addition of this datacenter (cines), I
> have a second FC data center (abes) in the same engine but which
> deals only with el6 hosts and upgrade to vdsm was fine for itself.
>
> Le 17/06/2015 15:17, Nathanaël Blanchet a écrit :
>
> Hello Aharon, I have 3 hosts in that domain : fuji, fuego, siple.
> thank you for your help
>
> Le 17/06/2015 15:10, Aharon Canan a écrit :
>
> Can you attach engine and vdsm logs ?
>
>
>
>
> Regards,
> __________________________________________________
> *Aharon Canan*
>
>
> ------------------------------------------------------------------------
>
> *From: *"Nathanaël Blanchet" <blanchet at abes.fr>
> *To: *users at ovirt.org
> *Sent: *Wednesday, June 17, 2015 4:03:29 PM
> *Subject: *[ovirt-users] storage domain don't go
> active anymore after 3.5.3 update
>
> Hello, since the update to 3.5.3, my master data
> domain fails to activate.
> I don't know what to do, and it is critical for
> production.
> Vms are still up but I can't interacte with them anymore
> If I shutdown any of them, I won't be able to recover
> them.
>
> My datacenter is a FC one, and all of my hosts have
> been upgraded to
> vdsm 4.16.20, I restarted vdsmd and engine, but
> nothing has changed.
>
> Thank you for your help.
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax 33 (0)4 67 54 84 14
> blanchet at abes.fr
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax 33 (0)4 67 54 84 14
> blanchet at abes.fr
>
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax 33 (0)4 67 54 84 14
> blanchet at abes.fr
>
>
--
Nathanaël Blanchet
Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
blanchet at abes.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150617/534e4004/attachment-0001.html>
More information about the Users
mailing list