Hi David,

just spotted this post from a couple of weeks ago -- I have the same
problem (Gluster volume not healing) since the upgrade from 7.x to 8.4.
Same exact errors on glustershd.log -- and same errors if I try to heal
manually.

Typically I can get the volume healed by killing the specific brick
processes manually and forcing a volume start (to restart the failed
bricks).

Just wondering if you've got any progress on your side?

I have also tried to upgrade to 9.1 in one of the clusters (I have three
different ones affected) but didn't solve the issue.

Regards.
Marco

On Mon, 26 Apr 2021 at 21:55, David White via Users <[email protected]> wrote:

> I did have my /etc/hosts setup on all 3 of the oVirt Hosts in the format
> you described, with the exception of the trailing "host1" and "host2". I
> only had the FQDN in there.
>
> I had an outage of almost an hour this morning that may or may not be
> related to this. An "ETL Service" started, at which point a lot of things
> broke down, and I saw a lot of storage-related errors. Everything came back
> on its own, though.
>
> See my other thread that I just started on that topic.
> As of now, there are NOT indications that any of the volumes or disks are
> out of sync.
>
>
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, April 25, 2021 1:43 AM, Strahil Nikolov via Users <
> [email protected]> wrote:
>
> A/AAAA & PTR records are pretty important.
> As long as you setup your /etc/hosts jn the format like this you will be
> OK:
>
> 10.10.10.10 host1.anysubdomain.domain host1
> 10.10.10.11 host2.anysubdomain.domain host2
>
> Usually the hostname is defined for each peer in the
> /var/lib/glusterd/peers. Can you check the contents on all nodes ?
>
> Best Regards,
> Strahil Nikolov
>
> On Sat, Apr 24, 2021 at 21:57, David White via Users
> <[email protected]> wrote:
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/[email protected]/message/CYPYALTFM7ITZZENSI6R5E6ZNT7TRY5Y/
>
>
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/[email protected]/message/NU6PXEUVVSCHVUIYTJRFOO72ZCJBWGVG/
>
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/4YLOE6ZX4W4XXEY72Q5ZJIZDKMNPEDO2/

Reply via email to