Were you ever able to find a fix for this? I am facing the same problem and the case is similar to yours. We have a 6 node distributed-replicated Gluster, due to a network issue all servers got disconnected and upon recover one of the volumes started giving the same IO error. The files can be read as root but are giving error when read as vdsm. Everything else is as in your case including the oVirt versions. While doing a full dd if=IMAGE of=/dev/null allows the disk to be mounted on one server temporarily, upon reboot/restart it returns to failing with IO error. I had to create a completely new gluster volume and copy the disks from the failing volume as root to resolve this.

Did you create a bug report in Bugzilla for this?

Regards,

Hesham Ahmed

On Wed, Feb 5, 2020 at 1:01 AM Christian Reiss <email@christian-reiss.de> wrote:
Thanks for replying,

What I just wrote Stahil was:


ACL is correctly set:

# file: 5aab365f-b1b9-49d0-b011-566bf936a100
# owner: vdsm
# group: kvm
user::rw-
group::rw-
other::---

Doing a setfacl failed due to "Operation not supported", remounting with
acl, too:

[root@node01 ~]# mount -o remount,acl
/rhev/data-center/mnt/glusterSD/node01.dc-dus.dalason.net\:_ssd__storage/
/bin/sh: glusterfs: command not found

As I am running the oVirt node I am not sure how feasable down/upgrading
is. I think I am stuck with what I have.

Also, if this would be a permission issue, I would not be able to access
the file at all. Seems I can access some of it. And all of it when root
loaded the whole file first.


I also did, even if it was correctly set, the chown from the mountpoint
again, to no avail.


On 04/02/2020 21:53, Christian Reiss wrote:
>
> ACL is correctly set:
>
> # file: 5aab365f-b1b9-49d0-b011-566bf936a100
> # owner: vdsm
> # group: kvm
> user::rw-
> group::rw-
> other::---
>
> Doing a setfacl failed due to "Operation not supported", remounting with
> acl, too:
>
> [root@node01 ~]# mount -o remount,acl
> /rhev/data-center/mnt/glusterSD/node01.dc-dus.dalason.net\:_ssd__storage/
> /bin/sh: glusterfs: command not found
>
> As I am running the oVirt node I am not sure how feasable down/upgrading
> is. I think I am stuck with what I have.
>
> Also, if this would be a permission issue, I would not be able to access
> the file at all. Seems I can access some of it. And all of it when root
> loaded the whole file first.

--
with kind regards,
mit freundlichen Gruessen,

Christian Reiss
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/G2MOTXZU6AFAGV2GL6P5XBXHMCRFUM6F/