Re: [ovirt-users] Host cannot access the Storage Domain(s) attached to the Data Center
Dear Sir;
I thought also that it could be issue with multipath; so I have added to
multipathd.conf the below lines:-
blacklist {
wwid "*"
}
# multipath -ll
# iscsiadm -m discovery -t st -p X.X.X.X
X.X.X.X:3260,1 iqn.2006-01.com.openfiler:tsn.6f138bf1cc59
# multipath -ll
Best Regards
Fawzy Ibrahim
From: Raz Tamir
To: Fawzy Ibrahim
Sent: Friday, February 12, 2016 4:27 PM
Subject: Re: [ovirt-users] Host cannot access the Storage Domain(s)
attached to the Data Center
Hi,
Can you make sure the host sees the iscsi luns? From the host run:
# multipath -ll
If the output is nothing so please follow the below commands:
# iscsiadm -m discovery -t st -p ISCSI_IP
You should get list of iscsi targets
# iscsiadm -m node -l
This will login to all targets and should output list of luns
# multipath -ll
Try this and update in case the problem still exist
Thanks,
Raz Tamir
Red Hat Isreal
On Feb 10, 2016 20:47, "Fawzy Ibrahim" wrote:
Dear All;
>
>I have oVirt Engine Version: 3.5.6.2-1.el6 with three nodesrunning standard
>Centos 6.7 64bit.
>
>The main data storage storage is on OpenFiler iScsi volume.
>
>After rebooting the three nodes; the main data storage domain is down and all
>the three hosts are marked as "Non Operational"
>
>When I try to activate any host; I get the below error message:-
>
>"Host X cannot access the Storage Domain(s) attached to the Data
>Center Default. Setting Host state to Non-Operational."
>>
>I have attached the engine and vdsm log.
>
>Best Regards
>Fawzy Ibrahim
>
>___
>Users mailing list
>Users@ovirt.org
>http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
Can you give me the steps on how to run the VM using virsh on oVirt manager? I have tried that before but it asked for password and it did not accept the oVirt admin's password. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
Thanks for your real support. Until we get replies for option#1, what's the exact steps for option#2? - Original Message - From: Itamar Heim ih...@redhat.com To: Fawzy Ibrhim fawzy_ibr...@yahoo.com; users@ovirt.org users@ovirt.org Cc: Sent: Sunday, October 26, 2014 12:16 AM Subject: Re: [ovirt-users] CPU type is not supported On 10/25/2014 03:37 PM, Fawzy Ibrhim wrote: I have no such option on BIOS. Please; check this image http://goo.gl/1o85R2 option 1: discuss on libvirt mailing list how to change libvirt config if possible to ignore that flag for cpu model detection. option 2: not sure if libvirt actually verifies the cpu model you pass. i.e., if qemu reports that cpu model, maybe you can still pass it ignoring the detection logic. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
I have no such option on BIOS. Please; check this image http://goo.gl/1o85R2 From: Amador Pahim apa...@redhat.com To: Fawzy Ibrhim fawzy_ibr...@yahoo.com; users@ovirt.org users@ovirt.org Sent: Thursday, October 23, 2014 2:27 PM Subject: Re: [ovirt-users] CPU type is not supported On 10/23/2014 06:02 AM, Fawzy Ibrhim wrote: I tried to update BIOS to latest version but with no luck. Can you advise where in BIOS, I have to enable AES? I haven't such hardware, but googling I found this: http://i.stack.imgur.com/ljSei.png ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
I tried but it did not work. From: Dan Yasny dya...@gmail.com To: Fawzy Ibrhim fawzy_ibr...@yahoo.com Sent: Wednesday, October 15, 2014 6:04 PM Subject: Re: [ovirt-users] CPU type is not supported The Nehalem family was launched in 2009, Dell PE 6850 stopped shipping in 2007, when 9G series was launched. Are you sure these are actual Nehalem CPUs you have in there? Try to drop the cluster level lower than Nehalem, maybe something will pick up, but as far as I remember the Dell 8G series, they were the first to even have VT, and aren't that great for it. I know the server looks like a real beast, but a modern 1U pizzabox nowadays can deliver better performance and much more compute. On Wed, Oct 15, 2014 at 2:42 AM, Fawzy Ibrhim fawzy_ibr...@yahoo.com wrote: Dear All; I have DELL PowerEdge 6850 with two Intel(R) Xeon(TM) CPU 2.66GHz. The CPU has the below flags which does not include AES flag:- flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx est cid cx16 xtpr lahf_lm tpr_shadow I have installed Centos 6.5 64bit on it and I need to add it to the cluster Intel Nehalem Family. oVirt Engine Version is 3.4.3-1.el6. Cluster Compatibility Version is: 3.4 CPU type is: Intel Nehalm Family The installation started normally and stopped with error:- Host iScsi moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all # virsh -r capabilities capabilities host uuid2bbed3bb-c962-4ffc-8fbc-20c73663137c/uuid cpu archx86_64/arch modelcpu64-rhel6/model vendorIntel/vendor topology sockets='2' cores='2' threads='2'/ feature name='xtpr'/ feature name='cid'/ feature name='est'/ feature name='vmx'/ feature name='ds_cpl'/ feature name='monitor'/ feature name='dtes64'/ feature name='pbe'/ feature name='tm'/ feature name='ht'/ feature name='ss'/ feature name='acpi'/ feature name='ds'/ feature name='vme'/ /cpu power_management suspend_disk/ /power_management migration_features live/ uri_transports uri_transporttcp/uri_transport /uri_transports /migration_features topology cells num='1' cell id='0' cpus num='8' cpu id='0' socket_id='2' core_id='0' siblings='0,4'/ cpu id='1' socket_id='3' core_id='0' siblings='1,5'/ cpu id='2' socket_id='2' core_id='1' siblings='2,6'/ cpu id='3' socket_id='3' core_id='1' siblings='3,7'/ cpu id='4' socket_id='2' core_id='0' siblings='0,4'/ cpu id='5' socket_id='3' core_id='0' siblings='1,5'/ cpu id='6' socket_id='2' core_id='1' siblings='2,6'/ cpu id='7' socket_id='3' core_id='1' siblings='3,7'/ /cpus /cell /cells /topology secmodel modelselinux/model doi0/doi /secmodel secmodel modeldac/model doi0/doi /secmodel /host guest os_typehvm/os_type arch name='i686' wordsize32/wordsize emulator/usr/libexec/qemu-kvm/emulator machinerhel6.5.0/machine machine canonical='rhel6.5.0'pc/machine machinerhel6.4.0/machine machinerhel6.3.0/machine machinerhel6.2.0/machine machinerhel6.1.0/machine machinerhel6.0.0/machine machinerhel5.5.0/machine machinerhel5.4.4/machine machinerhel5.4.0/machine domain type='qemu' /domain domain type='kvm' emulator/usr/libexec/qemu-kvm/emulator /domain /arch features cpuselection/ deviceboot/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ pae/ nonpae/ /features /guest guest os_typehvm/os_type arch name='x86_64' wordsize64/wordsize emulator/usr/libexec/qemu-kvm/emulator machinerhel6.5.0/machine machine canonical='rhel6.5.0'pc/machine machinerhel6.4.0/machine machinerhel6.3.0/machine machinerhel6.2.0/machine machinerhel6.1.0/machine machinerhel6.0.0/machine machinerhel5.5.0/machine machinerhel5.4.4/machine machinerhel5.4.0/machine domain type='qemu' /domain domain type='kvm' emulator/usr/libexec/qemu-kvm/emulator /domain /arch features cpuselection/ deviceboot/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ /features /guest /capabilities ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
# vdsClient -s 0 getVdsCaps | grep cpu cpuCores = '4' cpuFlags = 'fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,lm,constant_tsc,pebs,bts,pni,dtes64,monitor,ds_cpl,vmx,est,cid,cx16,xtpr,lahf_lm,tpr_shadow,model_coreduo' cpuModel = 'Intel(R) Xeon(TM) CPU 2.66GHz' cpuSockets = '2' cpuSpeed = '2659.934' cpuThreads = '8'___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
I tried to update BIOS to latest version but with no luck. Can you advise where in BIOS, I have to enable AES?___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] CPU type is not supported
Dear All; I have DELL PowerEdge 6850 with two Intel(R) Xeon(TM) CPU 2.66GHz. The CPU has the below flags which does not include AES flag:- flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx est cid cx16 xtpr lahf_lm tpr_shadow I have installed Centos 6.5 64bit on it and I need to add it to the cluster Intel Nehalem Family. oVirt Engine Version is 3.4.3-1.el6. Cluster Compatibility Version is: 3.4 CPU type is: Intel Nehalm Family The installation started normally and stopped with error:- Host iScsi moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all # virsh -r capabilities capabilities host uuid2bbed3bb-c962-4ffc-8fbc-20c73663137c/uuid cpu archx86_64/arch modelcpu64-rhel6/model vendorIntel/vendor topology sockets='2' cores='2' threads='2'/ feature name='xtpr'/ feature name='cid'/ feature name='est'/ feature name='vmx'/ feature name='ds_cpl'/ feature name='monitor'/ feature name='dtes64'/ feature name='pbe'/ feature name='tm'/ feature name='ht'/ feature name='ss'/ feature name='acpi'/ feature name='ds'/ feature name='vme'/ /cpu power_management suspend_disk/ /power_management migration_features live/ uri_transports uri_transporttcp/uri_transport /uri_transports /migration_features topology cells num='1' cell id='0' cpus num='8' cpu id='0' socket_id='2' core_id='0' siblings='0,4'/ cpu id='1' socket_id='3' core_id='0' siblings='1,5'/ cpu id='2' socket_id='2' core_id='1' siblings='2,6'/ cpu id='3' socket_id='3' core_id='1' siblings='3,7'/ cpu id='4' socket_id='2' core_id='0' siblings='0,4'/ cpu id='5' socket_id='3' core_id='0' siblings='1,5'/ cpu id='6' socket_id='2' core_id='1' siblings='2,6'/ cpu id='7' socket_id='3' core_id='1' siblings='3,7'/ /cpus /cell /cells /topology secmodel modelselinux/model doi0/doi /secmodel secmodel modeldac/model doi0/doi /secmodel /host guest os_typehvm/os_type arch name='i686' wordsize32/wordsize emulator/usr/libexec/qemu-kvm/emulator machinerhel6.5.0/machine machine canonical='rhel6.5.0'pc/machine machinerhel6.4.0/machine machinerhel6.3.0/machine machinerhel6.2.0/machine machinerhel6.1.0/machine machinerhel6.0.0/machine machinerhel5.5.0/machine machinerhel5.4.4/machine machinerhel5.4.0/machine domain type='qemu' /domain domain type='kvm' emulator/usr/libexec/qemu-kvm/emulator /domain /arch features cpuselection/ deviceboot/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ pae/ nonpae/ /features /guest guest os_typehvm/os_type arch name='x86_64' wordsize64/wordsize emulator/usr/libexec/qemu-kvm/emulator machinerhel6.5.0/machine machine canonical='rhel6.5.0'pc/machine machinerhel6.4.0/machine machinerhel6.3.0/machine machinerhel6.2.0/machine machinerhel6.1.0/machine machinerhel6.0.0/machine machinerhel5.5.0/machine machinerhel5.4.4/machine machinerhel5.4.0/machine domain type='qemu' /domain domain type='kvm' emulator/usr/libexec/qemu-kvm/emulator /domain /arch features cpuselection/ deviceboot/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ /features /guest /capabilities ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
I tried to follow this guide https://www.berrange.com/posts/2010/02/15/guest-cpu-model-configuration-in-libvirt-with-qemukvm/ I found that the host that has the problem has no pbe|tm|ht||acpi|ds flags in output of cat /proc/cpuinfo In the Ovirt-Engine server I run the below:- #virsh -r cpu-compare ./cpu-server.xml CPU described in ./cpu-server.xml is incompatible with host CPU #virsh -r cpu-baseline ./cpu-server.xml cpu mode='custom' match='exact' model fallback='allow'cpu64-rhel6/model vendorIntel/vendor feature policy='require' name='xtpr'/ feature policy='require' name='cid'/ feature policy='require' name='est'/ feature policy='require' name='vmx'/ feature policy='require' name='ds_cpl'/ feature policy='require' name='monitor'/ feature policy='require' name='dtes64'/ feature policy='require' name='pbe'/ feature policy='require' name='tm'/ feature policy='require' name='ht'/ feature policy='require' name='ss'/ feature policy='require' name='acpi'/ feature policy='require' name='ds'/ feature policy='require' name='vme'/ /cpu Is there any workaround for this issue? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
I tried to follow this guide https://www.berrange.com/posts/2010/02/15/guest-cpu-model-configuration-in-libvirt-with-qemukvm/ I found that the host that has the proble has no pbe|tm|ht||acpi|ds flags in output of cat /proc/cpuinfo In the Ovirt-Engine server I run the below #virsh -r cpu-compare ./cpu-server.xml CPU described in ./cpu-server.xml is incompatible with host CPU #virsh -r cpu-baseline ./cpu-server.xml cpu mode='custom' match='exact' model fallback='allow'cpu64-rhel6/model vendorIntel/vendor feature policy='require' name='xtpr'/ feature policy='require' name='cid'/ feature policy='require' name='est'/ feature policy='require' name='vmx'/ feature policy='require' name='ds_cpl'/ feature policy='require' name='monitor'/ feature policy='require' name='dtes64'/ feature policy='require' name='pbe'/ feature policy='require' name='tm'/ feature policy='require' name='ht'/ feature policy='require' name='ss'/ feature policy='require' name='acpi'/ feature policy='require' name='ds'/ feature policy='require' name='vme'/ /cpu ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
I tried to follow this guide Daniel P. Berrangé » Blog Archive » Guest CPU model configuration in libvirt with QEMU/KVM I found that the host that has the proble has no pbe|tm|ht||acpi|ds flags in output of cat /proc/cpuinfo In the Ovirt-Engine server I run the below #virsh -r cpu-compare ./cpu-server.xml CPU described in ./cpu-server.xml is incompatible with host CPU #virsh -r cpu-baseline ./cpu-server.xml cpu mode='custom' match='exact' model fallback='allow'cpu64-rhel6/model vendorIntel/vendor feature policy='require' name='xtpr'/ feature policy='require' name='cid'/ feature policy='require' name='est'/ feature policy='require' name='vmx'/ feature policy='require' name='ds_cpl'/ feature policy='require' name='monitor'/ feature policy='require' name='dtes64'/ feature policy='require' name='pbe'/ feature policy='require' name='tm'/ feature policy='require' name='ht'/ feature policy='require' name='ss'/ feature policy='require' name='acpi'/ feature policy='require' name='ds'/ feature policy='require' name='vme'/ /cpu Is there any workaround for this issue Daniel P. Berrangé » Blog Archive » Guest CPU model configuration in libvirt with QEMU/KVM Guest CPU model configuration in libvirt with QEMU/KVM Posted: February 15th, 2010 | Author: Daniel Berrange | Filed under: libvirt, Virt Tools | 5 Comments » View on www.berrange.com Preview by Yahoo From: Fawzy Ibrhim fawzy_ibr...@yahoo.com To: Sven Kieske s.kie...@mittwald.de; users@ovirt.org users@ovirt.org Sent: Wednesday, September 3, 2014 9:15 PM Subject: Re: [ovirt-users] CPU type is not supported I have found the below workaround:- Xeon 5060 support Dempsey - Emulators Ovirt User Xeon 5060 support Dempsey - Emulators Ovirt User Emulators Discussion Forums : Xeon 5060 support Dempsey - Emulators Ovirt User View on t360192.emulators-ovirt-user.emulatortalk.info Preview by Yahoo From: Fawzy Ibrhim fawzy_ibr...@yahoo.com To: Sven Kieske s.kie...@mittwald.de; users@ovirt.org users@ovirt.org Sent: Wednesday, September 3, 2014 8:49 AM Subject: Re: [ovirt-users] CPU type is not supported Cluster Compatibility Version is: 3.4 CPU type is: Intel Nehalm Family ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
I have found the below workaround:- Xeon 5060 support Dempsey - Emulators Ovirt User Xeon 5060 support Dempsey - Emulators Ovirt User Emulators Discussion Forums : Xeon 5060 support Dempsey - Emulators Ovirt User View on t360192.emulators-ovirt-user.emulatortalk.info Preview by Yahoo From: Fawzy Ibrhim fawzy_ibr...@yahoo.com To: Sven Kieske s.kie...@mittwald.de; users@ovirt.org users@ovirt.org Sent: Wednesday, September 3, 2014 8:49 AM Subject: Re: [ovirt-users] CPU type is not supported Cluster Compatibility Version is: 3.4 CPU type is: Intel Nehalm Family From: Sven Kieske s.kie...@mittwald.de To: users@ovirt.org users@ovirt.org Sent: Tuesday, September 2, 2014 10:20 AM Subject: Re: [ovirt-users] CPU type is not supported So what is your cluster compatibility version? which cpu type did you select in ovirt? nobody can help you without this information. Am 01.09.2014 22:37, schrieb Fawzy Ibrhim: The installation started normally and stopped with error:- Host iScsi moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] CPU type is not supported
Cluster Compatibility Version is: 3.4 CPU type is: Intel Nehalm Family From: Sven Kieske s.kie...@mittwald.de To: users@ovirt.org users@ovirt.org Sent: Tuesday, September 2, 2014 10:20 AM Subject: Re: [ovirt-users] CPU type is not supported So what is your cluster compatibility version? which cpu type did you select in ovirt? nobody can help you without this information. Am 01.09.2014 22:37, schrieb Fawzy Ibrhim: The installation started normally and stopped with error:- Host iScsi moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] CPU type is not supported
Dear All; I have DELL PowerEdge 6850 with two Intel(R) Xeon(TM) CPU 2.66GHz. The CPU has the below flags which does not include AES flag:- flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc pebs bts pni dtes64 monitor ds_cpl vmx est cid cx16 xtpr lahf_lm tpr_shadow I have installed Centos 6.5 64bit on it and I need to add it to cluster Intel Nehalem Family. Our oVirt Engine Version is 3.4.3-1.el6. The installation started normally and stopped with error:- Host iScsi moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all # virsh -r capabilities capabilities host uuid2bbed3bb-c962-4ffc-8fbc-20c73663137c/uuid cpu archx86_64/arch modelcpu64-rhel6/model vendorIntel/vendor topology sockets='2' cores='2' threads='2'/ feature name='xtpr'/ feature name='cid'/ feature name='est'/ feature name='vmx'/ feature name='ds_cpl'/ feature name='monitor'/ feature name='dtes64'/ feature name='pbe'/ feature name='tm'/ feature name='ht'/ feature name='ss'/ feature name='acpi'/ feature name='ds'/ feature name='vme'/ /cpu power_management suspend_disk/ /power_management migration_features live/ uri_transports uri_transporttcp/uri_transport /uri_transports /migration_features topology cells num='1' cell id='0' cpus num='8' cpu id='0' socket_id='2' core_id='0' siblings='0,4'/ cpu id='1' socket_id='3' core_id='0' siblings='1,5'/ cpu id='2' socket_id='2' core_id='1' siblings='2,6'/ cpu id='3' socket_id='3' core_id='1' siblings='3,7'/ cpu id='4' socket_id='2' core_id='0' siblings='0,4'/ cpu id='5' socket_id='3' core_id='0' siblings='1,5'/ cpu id='6' socket_id='2' core_id='1' siblings='2,6'/ cpu id='7' socket_id='3' core_id='1' siblings='3,7'/ /cpus /cell /cells /topology secmodel modelselinux/model doi0/doi /secmodel secmodel modeldac/model doi0/doi /secmodel /host guest os_typehvm/os_type arch name='i686' wordsize32/wordsize emulator/usr/libexec/qemu-kvm/emulator machinerhel6.5.0/machine machine canonical='rhel6.5.0'pc/machine machinerhel6.4.0/machine machinerhel6.3.0/machine machinerhel6.2.0/machine machinerhel6.1.0/machine machinerhel6.0.0/machine machinerhel5.5.0/machine machinerhel5.4.4/machine machinerhel5.4.0/machine domain type='qemu' /domain domain type='kvm' emulator/usr/libexec/qemu-kvm/emulator /domain /arch features cpuselection/ deviceboot/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ pae/ nonpae/ /features /guest guest os_typehvm/os_type arch name='x86_64' wordsize64/wordsize emulator/usr/libexec/qemu-kvm/emulator machinerhel6.5.0/machine machine canonical='rhel6.5.0'pc/machine machinerhel6.4.0/machine machinerhel6.3.0/machine machinerhel6.2.0/machine machinerhel6.1.0/machine machinerhel6.0.0/machine machinerhel5.5.0/machine machinerhel5.4.4/machine machinerhel5.4.0/machine domain type='qemu' /domain domain type='kvm' emulator/usr/libexec/qemu-kvm/emulator /domain /arch features cpuselection/ deviceboot/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ /features /guest /capabilities___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Volume XXX contains a apparently corrupt brick(s).
Dear All;
I have GlusterFS storage domain in my oVirt Engine Version: 3.4.3-1.el6.
One of the peers get disconnected due to network cable unplugged and after that
I failed to add/remove disks from my GlusterFS domain.
I have healed the GlusterFS volume and removed the corrupted index file and
healed the GlusterFS volume.
As workaround, I have stopped all the VM and put the GlusterFS domian in
maintenance mode and activated it again and now I can add/remove disks from the
GlusterFS domain.
But I still have the below warnings in my ovirt-engine.log:-
2014-09-01 23:09:47,550 WARN
[org.ovirt.engine.core.bll.gluster.GlusterSyncJob]
(DefaultQuartzScheduler_Worker-26) Volume XXX contains a apparently corrupt
brick(s). Hence will not add it to engine at this point.
2014-09-01 23:09:52,558 INFO
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand]
(DefaultQuartzScheduler_Worker-61) START, GlusterVolumesListVDSCommand(HostName
= host1, HostId = 0de0e7d7-a3dd-4776-9393-c36b8c4b452d), log id: 2b6381b0
2014-09-01 23:09:52,588 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc]
(DefaultQuartzScheduler_Worker-61) Could not add brick
host2:/var/lib/exports/gluster/brick1 to volume
fca9d8a4-392d-4e55-a2ac-8e09a75c5cd2 - server uuid
d7763283-10b6-4880-a7b3-48d0353205b0 not found in cluster
0001-0001-0001-0001-033a
2014-09-01 23:09:52,594 INFO
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand]
(DefaultQuartzScheduler_Worker-61) FINISH, GlusterVolumesListVDSCommand,
return:
{fca9d8a4-392d-4e55-a2ac-8e09a75c5cd2=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@107254ac},
log id: 2b6381b0
Best Regards
Fawzy Ibrahim
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
