As far as I know, oVirt 4.4 uses gluster v7.X , so you will eventually have
to upgrade the version.
As I mentioned, I have created my new volume while I was running a higher
version and copied the data to it, which prevented the acl bug hitting me
again.
I can recommend you to:
1. Mou
As I told you, you could just downgrade gluster on all nodes and later plan to
live migrate the VM disks.
I had to copy my data to the new volume, so I can avoid the ACL bug , when I
use newer versions of gluster.
Let's clarify some details:
1. Which version of oVirt and Gluster are you using
Strahil,
I have downgraded the target. The copy from the problematic volume to the
target is going on now.
Once I have the data copied, I might downgrade the problematic volume's
Gluster to 6.5.
At that point I might reattach the original ovirt domain and see if it will
work again.
But the copy is
You should ensure that in the storage domain tab, the old storage is not
visible.
I still wander why yoiu didn't try to downgrade first.
Best Regards,
Strahil Nikolov
На 22 юни 2020 г. 13:58:33 GMT+03:00, C Williams
написа:
>Strahil,
>
>The GLCL3 storage domain was detached prior to attemp
4 matches
Mail list logo
