<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 24, 2017 at 2:53 PM, Nithya Balachandran <span dir="ltr"><<a href="mailto:nbalacha@redhat.com" target="_blank">nbalacha@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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></blockquote><div><br></div><div>Thanks Nithya. @Rafi, @Raghavendra Bhat, is it possible to take the ownership of,</div><div><br></div><div>* Identifying whether the patch in question causes the issue?</div><div>* Send a fix or at least evaluate whether a fix is possible.<br></div><div><br></div><div>@Others,</div><div><br></div><div>With the motivation of getting some traction on this, Is it ok if we:</div><div>* Set a deadline of around 15 days to complete the review (or testing with the patch in question) of respective components and to come up with issues (if any).</div><div>* Post the deadline, if there are no open issues, go ahead and merge the patch?</div><div><br></div><div>If time is not enough, let us know and we can come up with a reasonable time.</div><div><br></div><div>regards,</div><div>Raghavendra</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 24 August 2017 at 10:13, Raghavendra G <span dir="ltr"><<a href="mailto:raghavendra.hg@gmail.com" target="_blank">raghavendra.hg@gmail.com</a>></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'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>"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"<br><br></div>regards,<br></div>Raghavendra<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-6469957665123384590h5">On Wed, Aug 23, 2017 at 11:56 AM, Raghavendra Gowdappa <span dir="ltr"><<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>></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="m_-6469957665123384590h5">Thanks Pranith and Ashish for your inputs.<br>
<span><br>
----- Original Message -----<br>
> From: "Pranith Kumar Karampuri" <<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>><br>
> To: "Ashish Pandey" <<a href="mailto:aspandey@redhat.com" target="_blank">aspandey@redhat.com</a>><br>
</span><span>> Cc: "Raghavendra Gowdappa" <<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>>, "Xavier Hernandez" <<a href="mailto:xhernandez@datalab.es" target="_blank">xhernandez@datalab.es</a>>, "Gluster Devel"<br>
> <<a href="mailto:gluster-devel@gluster.org" target="_blank">gluster-devel@gluster.org</a>><br>
</span><span>> Sent: Wednesday, August 23, 2017 11:55:19 AM<br>
> Subject: Re: Need inputs on patch #17985<br>
><br>
> Raghavendra,<br>
> As Ashish mentioned, there aren't any known problems if upper xlators<br>
> don't send lookups in EC at the moment.<br>
><br>
> On Wed, Aug 23, 2017 at 9:07 AM, Ashish Pandey <<a href="mailto:aspandey@redhat.com" target="_blank">aspandey@redhat.com</a>> wrote:<br>
><br>
> > Raghvendra,<br>
> ><br>
> > I have provided my comment on this patch.<br>
> > I think EC will not have any issue with this approach.<br>
> > However, I would welcome comments from Xavi and Pranith too for any side<br>
> > effects which I may not be able to foresee.<br>
> ><br>
> > Ashish<br>
> ><br>
</span>> > ------------------------------<br>
> > *From: *"Raghavendra Gowdappa" <<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>><br>
> > *To: *"Ashish Pandey" <<a href="mailto:aspandey@redhat.com" target="_blank">aspandey@redhat.com</a>><br>
> > *Cc: *"Pranith Kumar Karampuri" <<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>>, "Xavier Hernandez"<br>
<span>> > <<a href="mailto:xhernandez@datalab.es" target="_blank">xhernandez@datalab.es</a>>, "Gluster Devel" <<a href="mailto:gluster-devel@gluster.org" target="_blank">gluster-devel@gluster.org</a>><br>
</span>> > *Sent: *Wednesday, August 23, 2017 8:29:48 AM<br>
> > *Subject: *Need inputs on patch #17985<br>
<span class="m_-6469957665123384590m_3449072565299201271im m_-6469957665123384590m_3449072565299201271HOEnZb">> ><br>
> ><br>
> > Hi Ashish,<br>
> ><br>
> > Following are the blockers for making a decision on whether patch [1] can<br>
> > be merged or not:<br>
> > * Evaluation of dentry operations (like rename etc) in dht<br>
> > * Whether EC works fine if a non-lookup fop (like open(dir), stat, chmod<br>
> > etc) hits EC without a single lookup performed on file/inode<br>
> ><br>
> > Can you please comment on the patch? I'll take care of dht part.<br>
> ><br>
> > [1] <a href="https://review.gluster.org/#/c/17985/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c<wbr>/17985/</a><br>
> ><br>
> > regards,<br>
> > Raghavendra<br>
> ><br>
> ><br>
><br>
><br>
> --<br>
> Pranith<br>
><br>
</span></div></div><div class="m_-6469957665123384590m_3449072565299201271HOEnZb"><div class="m_-6469957665123384590m_3449072565299201271h5"><div><div class="m_-6469957665123384590h5">______________________________<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="m_-6469957665123384590HOEnZb"><font color="#888888"><br clear="all"><br>-- <br><div class="m_-6469957665123384590m_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" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Raghavendra G<br></div>
</div></div>