[ovirt-users] Re: Sometimes paused due to unknown storage error on gluster

On Wed, Apr 8, 2020 at 6:00 PM Strahil Nikolov <hunter86_bg(a)yahoo.com&gt; wrote: I deployed oVirt 4.3.9 using ovirt-node-ng iso image and using cockpit based GUI wizard for HCI one node. And on ovirt-node-ng system the version was the latest available in stable 4.3 ovirt repos: glusterfs-6.8-1.el7.x86_64 The same if I go on a plain CentOS ovirt host of another environment, fully updated, the version for gluster related packages is 6.8-1.el7 and no update proposed. So I think I'm ok with that. Ah, ok. In my case I have single host environment, so in my case is not fundamental, and no upgrade has took place yet from the original 4.3.9 deploy, I have: [root@ovirt images]# gluster volume get all cluster.op-version Option Value ------ ----- cluster.op-version 60000 [root@ovirt images]# [root@ovirt images]# gluster volume get all cluster.max-op-version Option Value ------ ----- cluster.max-op-version 60000 [root@ovirt images]# I also take in great consideration Red Hat documentation. But at the end the product is upstream, and I don't find anything in upstream documentation related to sharding (only for old 3.7 days...). Why? Or where is the doc if it is my fault? Otherwise this lets me take attention about the stability of the feature.... Remember: I have only one node and only one brick per volume, so it doesn't give me any real benefit I think If I go and add another node I'll take care to modify, but it is not an immediate thing. It is a test lab Not needed in my environment 2. When a heal is going on, the shard is locked - so there will be no No heal on my environment because it is distributed (even if actually I have one brick per volume) Where do you see that the default is 64MB? Gluster what? upstream 6.8 or at build time by the team to create ovirt-4.3-centos-gluster6 repos or what? Because if you read the Red Hat Gluster Storage documentation (that you referred as the "master") it says that 512MB is the default and apparently the only allowed in their product.... As I already linked: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5... " features.shard-block-size Specifies the maximum size of the file pieces when sharding is enabled. The supported value for this parameter is 512MB. " And also in the table here: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5... you can see that both Alowed and Default values are 512MB I don't know if the Red Hat Gluster Storage 3.5 product is based on 6.8 version or not? How to check? And, missing the upstream documentation about sharding values, I cannot compare to that.... But as the RHV 4.3 product guide directly refers to Red Hat Gluster Storage docs.... I imagine what provided by oVirt is in the same version line.... OK, thanks In fact I created another 4Tb volume and disabled sharding on it. Then today I deployed again the Openshift OCP installation using 3 Master Nodes + 7 Worker Nodes, each with a 120Gb disk (thin provisioned) and the installation completed without any storage unknown error. Before I tried 3 times the same installation and every time I got at least 4-5 nodes that during the installation phase with ignition process from bootstrap node went to paused.... This + the gfid errors I provided seem to confirm my idea. In the future it can grow to more than one node. And also I wante to use / test a supported one node configuration for oVirt. And also many ansible scripts used take advantage of ovirt modules: https://docs.ansible.com/ansible/latest/modules/ovirt_module.html Cheers, Gianluca