On February 24, 2020 7:50:15 PM GMT+02:00, Hesham Ahmed <hsah...@gmail.com> 
wrote:
>In my case I am continuing with oVirt node 4.3.8 based gluster 6.7 for
>the
>time being. I have resolved the issue by manually copying all disk
>images
>to a new gluster volume which took days specially since disks on
>gluster
>still don't support sparse file copy. But the threat of a temporary
>network
>failure bringing down the complete oVirt setup is a bit too much risk.
>
>On Mon, Feb 24, 2020 at 9:29 PM Christian Reiss
><em...@christian-reiss.de>
>wrote:
>
>> Hey,
>>
>> I do not have the faulty cluster anymore; It's a production
>environment
>> with HA requirements so I really cant take it down for days or even
>> worse, weeks.
>>
>> I am now running of CentOS7 (manual install) with manual Gluster 7.0
>> installation and current ovirt. So far so good.
>>
>> Time will tell :)
>>
>> On 24/02/2020 18:11, Strahil Nikolov wrote:
>> > On February 24, 2020 5:10:40 PM GMT+02:00, Hesham Ahmed <
>> hsah...@gmail.com> wrote:
>> >> My issue is with Gluster 6.7 (the default with oVirt 4.3.7) as is
>the
>> >> case
>> >> with Christian. I still have the failing volume and disks and can
>share
>> >> any
>> >> information required.
>>
>>
>> --
>> with kind regards,
>> mit freundlichen Gruessen,
>>
>> Christian Reiss
>>
>>

Hey Hesham,

Do you keep the old  volumes?
Maybe you can assist Ravi on debugging this issue ?

Best Regards,
Strahil Nikolov
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FIAZRQMTFSDPOV6OKVOOU7OAORJVXQDY/

Reply via email to