<div dir="ltr">It has been a while but iirc snapview client (loaded abt dht/tier etc) had some issues when we ran tiering tests. Rafi might have more info on this - basically it was expecting to find the inode_ctx populated but it was not.</div><div class="gmail_extra"><br><div class="gmail_quote">On 24 August 2017 at 10:13, Raghavendra G <span dir="ltr">&lt;<a href="mailto:raghavendra.hg@gmail.com" target="_blank">raghavendra.hg@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>Note that we need to consider xlators on brick stack too. I&#39;ve added maintainers/peers of xlators on brick stack. Please explicitly ack/nack whether this patch affects your component.<br><br></div>For reference, following are the xlators loaded in brick stack<br><br></div>storage/posix<br></div>features/trash<br>features/changetimerecorder<br>features/changelog<br>features/bitrot-stub<br>features/access-control<br>features/locks<br>features/worm<br>features/read-only<br>features/leases<br>features/upcall<br>performance/io-threads<br>features/selinux<br>features/marker<br>features/barrier<br>features/index<br>features/quota<br>debug/io-stats<br>performance/decompounder<br>protocol/server<br><br><br></div>For those not following this thread, the question we need to answer is,<br></div>&quot;whether the xlator you are associated with works fine if a non-lookup fop (like open, setattr, stat etc) hits it without a lookup ever being done on that inode&quot;<br><br></div>regards,<br></div>Raghavendra<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Wed, Aug 23, 2017 at 11:56 AM, Raghavendra Gowdappa <span dir="ltr">&lt;<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>&gt;</span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Thanks Pranith and Ashish for your inputs.<br>
<span><br>
----- Original Message -----<br>
&gt; From: &quot;Pranith Kumar Karampuri&quot; &lt;<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>&gt;<br>
&gt; To: &quot;Ashish Pandey&quot; &lt;<a href="mailto:aspandey@redhat.com" target="_blank">aspandey@redhat.com</a>&gt;<br>
</span><span>&gt; Cc: &quot;Raghavendra Gowdappa&quot; &lt;<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>&gt;, &quot;Xavier Hernandez&quot; &lt;<a href="mailto:xhernandez@datalab.es" target="_blank">xhernandez@datalab.es</a>&gt;, &quot;Gluster Devel&quot;<br>
&gt; &lt;<a href="mailto:gluster-devel@gluster.org" target="_blank">gluster-devel@gluster.org</a>&gt;<br>
</span><span>&gt; Sent: Wednesday, August 23, 2017 11:55:19 AM<br>
&gt; Subject: Re: Need inputs on patch #17985<br>
&gt;<br>
&gt; Raghavendra,<br>
&gt;     As Ashish mentioned, there aren&#39;t any known problems if upper xlators<br>
&gt; don&#39;t send lookups in EC at the moment.<br>
&gt;<br>
&gt; On Wed, Aug 23, 2017 at 9:07 AM, Ashish Pandey &lt;<a href="mailto:aspandey@redhat.com" target="_blank">aspandey@redhat.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Raghvendra,<br>
&gt; &gt;<br>
&gt; &gt; I have provided my comment on this patch.<br>
&gt; &gt; I think EC will not have any issue with this approach.<br>
&gt; &gt; However, I would welcome comments from Xavi and Pranith too for any side<br>
&gt; &gt; effects which I may not be able to foresee.<br>
&gt; &gt;<br>
&gt; &gt; Ashish<br>
&gt; &gt;<br>
</span>&gt; &gt; ------------------------------<br>
&gt; &gt; *From: *&quot;Raghavendra Gowdappa&quot; &lt;<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>&gt;<br>
&gt; &gt; *To: *&quot;Ashish Pandey&quot; &lt;<a href="mailto:aspandey@redhat.com" target="_blank">aspandey@redhat.com</a>&gt;<br>
&gt; &gt; *Cc: *&quot;Pranith Kumar Karampuri&quot; &lt;<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>&gt;, &quot;Xavier Hernandez&quot;<br>
<span>&gt; &gt; &lt;<a href="mailto:xhernandez@datalab.es" target="_blank">xhernandez@datalab.es</a>&gt;, &quot;Gluster Devel&quot; &lt;<a href="mailto:gluster-devel@gluster.org" target="_blank">gluster-devel@gluster.org</a>&gt;<br>
</span>&gt; &gt; *Sent: *Wednesday, August 23, 2017 8:29:48 AM<br>
&gt; &gt; *Subject: *Need inputs on patch #17985<br>
<span class="m_3449072565299201271im m_3449072565299201271HOEnZb">&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Hi Ashish,<br>
&gt; &gt;<br>
&gt; &gt; Following are the blockers for making a decision on whether patch [1] can<br>
&gt; &gt; be merged or not:<br>
&gt; &gt; * Evaluation of dentry operations (like rename etc) in dht<br>
&gt; &gt; * Whether EC works fine if a non-lookup fop (like open(dir), stat, chmod<br>
&gt; &gt; etc) hits EC without a single lookup performed on file/inode<br>
&gt; &gt;<br>
&gt; &gt; Can you please comment on the patch? I&#39;ll take care of dht part.<br>
&gt; &gt;<br>
&gt; &gt; [1] <a href="https://review.gluster.org/#/c/17985/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c<wbr>/17985/</a><br>
&gt; &gt;<br>
&gt; &gt; regards,<br>
&gt; &gt; Raghavendra<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Pranith<br>
&gt;<br>
</span></div></div><div class="m_3449072565299201271HOEnZb"><div class="m_3449072565299201271h5"><div><div class="h5">______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
</div></div><a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel<span class="HOEnZb"><font color="#888888"><br clear="all"><br>-- <br><div class="m_3449072565299201271gmail_signature" data-smartmail="gmail_signature">Raghavendra G<br></div>
<br></font></span></a></div>
</div></blockquote></div></div>
<br>______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br></blockquote></div><br></div>