+++ This bug was initially created as a clone of Bug #1418900 +++ Description of problem: ----------------------- There are some volume options that needs to be added to virt file network.remote-dio=off features.shard-block-size=4MB performance.low-prio-threads=32 cluster.locking-scheme=granular cluster.shd-max-threads=8 cluster.shd-wait-qlength=10000 performance.strict-o-direct=on user.cifs=off nfs.disable=on cluster.use-compound-fops=on Version-Release number of selected component (if applicable): ------------------------------------------------------------- mainline How reproducible: ----------------- Not applicable Steps to Reproduce: ------------------- Not applicable Actual results: --------------- Not applicable Expected results: ----------------- Few more options added to virt file Additional info: ---------------- granular-entry-heal also needs to be enabled on the volume, but this option could only be added unless the volume is started.
upstream patch : https://review.gluster.org/16577
https://code.engineering.redhat.com/gerrit/#/c/98122/1
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/98122
Tested with glusterfs-3.8.4-15.el7rhgs [root@ ~]# rpm -qf /var/lib/glusterd/groups/virt glusterfs-server-3.8.4-15.el7rhgs.x86_64 [root@ ~]# cat /var/lib/glusterd/groups/virt performance.quick-read=off performance.read-ahead=off performance.io-cache=off performance.stat-prefetch=off performance.low-prio-threads=32 network.remote-dio=enable cluster.eager-lock=enable cluster.quorum-type=auto cluster.server-quorum-type=server cluster.data-self-heal-algorithm=full cluster.locking-scheme=granular cluster.shd-max-threads=8 cluster.shd-wait-qlength=10000 features.shard=on user.cifs=off 'virt' file has the required volume options
Atin, Any reason why features.shard-block-size is not set in the virt profile?.
(Satheesaran has already explained it over IRC) default shard-block-size is 4MB when features.shard is enabled
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0486.html