<div dir="ltr"><div><div>Yes. I apologise for the delay. <br><br></div>Disabling sharding would knock the translator itself off the client stack, and<br></div><div>being that sharding is the actual (and the only) translator that has the<br>knowledge of how to interpret sharded files, and how to aggregate them,<br>removing the translator from the stack will make all shards start to appear like<br></div><div>isolated files with no way to interpret the correlation between the individual pieces.<br><br></div><div>The only way to fix it is to have sharding be part of the graph *even* if disabled,<br>except that in this case, its job should be confined to aggregating the already<br>sharded files during reads but NOT shard new files that are created, since it is<br></div><div>supposed to "act" disabled. This is a slightly bigger change and this is why I had<br>suggested the workaround at <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1355846#c1">https://bugzilla.redhat.com/show_bug.cgi?id=1355846#c1</a><br>back then.<br></div><div><br></div><div>FWIW, the documentation [1] does explain how to disable sharding the right<br></div><div>way and has been in existence ever since sharding was first released in 3.7.0.<br><br>[1] - <a href="http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/shard/" target="_blank">http://staged-gluster-docs.<wbr>readthedocs.io/en/release3.7.<wbr>0beta1/Features/shard/</a><br><br></div><div>-Krutika<br></div><div><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 14, 2016 at 9:08 PM, Gandalf Corvotempesta <span dir="ltr"><<a href="mailto:gandalf.corvotempesta@gmail.com" target="_blank">gandalf.corvotempesta@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">2016-11-14 15:54 GMT+01:00 Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>>:<br>
> Obviously this is unacceptible for versions that have sharding as a<br>
> functional (not experimental) feature. All supported features are<br>
> expected to function without major problems (like corruption) for all<br>
> standard Gluster operations. Add-brick/replace-brick are surely such<br>
> Gluster operations.<br>
<br>
</span>Is sharding an experimental feature even in 3.8 ?<br>
Because in 3.8 announcement, it's declared stable:<br>
<a href="http://blog.gluster.org/2016/06/glusterfs-3-8-released/" rel="noreferrer" target="_blank">http://blog.gluster.org/2016/<wbr>06/glusterfs-3-8-released/</a><br>
"Sharding is now stable for VM image storage. "<br>
<span class=""><br>
> FWIW sharding has several open bugs (like any other component), but it<br>
> is not immediately clear to me if the problem reported in this email is<br>
> in Bugzilla yet. These are the bugs that are expected to get fixed in<br>
> upcoming minor releases:<br>
> <a href="https://bugzilla.redhat.com/buglist.cgi?component=sharding&f1=bug_status&f2=version&o1=notequals&o2=notequals&product=GlusterFS&query_format=advanced&v1=CLOSED&v2=mainline" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>buglist.cgi?component=<wbr>sharding&f1=bug_status&f2=<wbr>version&o1=notequals&o2=<wbr>notequals&product=GlusterFS&<wbr>query_format=advanced&v1=<wbr>CLOSED&v2=mainline</a><br>
<br>
</span>My issue with sharding was reported in bugzilla on 2016-07-12<br>
4 months for a IMHO, critical bug.<br>
<br>
If you disable sharding on a sharded volume with existing shared data,<br>
you corrupt every existing file.<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br>
</div></div></blockquote></div><br></div>