<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 13 July 2017 at 11:46, Pranith Kumar Karampuri <span dir="ltr"><<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Jul 13, 2017 at 10:11 AM, Taehwa Lee <span dir="ltr"><<a href="mailto:alghost.lee@gmail.com" target="_blank">alghost.lee@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 style="word-wrap:break-word"><div>Thank you for response quickly</div><div><br></div><div><br></div><div>I went through dht_get_du_info before I start developing this.</div><div><br></div><div>at that time, I think that this functionality should be independent module.</div><div><br></div><div><br></div><div>so, I will move this into DHT without new statfs.</div></div></blockquote><div><br></div></span></div></div></div></blockquote><div><br></div><div>Can you provide the details of your usecase? I ask because we already have dht redirecting creates to other subvols if a particular brick's usage crosses a certain value.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div></div></span><div>Let's here from dht folks also what they think about this change before you make modifications. I included some of the dht folks to the thread.<br></div><div><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>and then, will suggest it on gerrit ! </div><div><br></div><div><br></div><div>Thank you so much.</div><span><br><div>
<div style="word-wrap:break-word"><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br>------------------------------<wbr>-----------<br>Taehwa Lee<br>Gluesys Co.,Ltd.<br><a href="mailto:alghost.lee@gmail.com" target="_blank">alghost.lee@gmail.com</a><br>+82-10-3420-6114, +82-70-8785-6591<br>------------------------------<wbr>-----------</div></div>
</div>
<br></span><div><blockquote type="cite"><div>2017. 7. 13. 오후 1:06, Pranith Kumar Karampuri <<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>> 작성:</div><div><div class="m_8036603510263190773h5"><br class="m_8036603510263190773m_746561717897587908Apple-interchange-newline"><div><div dir="ltr"><div><div>hey,<br></div> I went through the patch. I see that statfs is always wound for create fop. So number of network operations increase and performance will be less even in normal case. I think similar functionality is in DHT, may be you should take a look at that?<br><br></div>Check dht_get_du_info() which is used by dht_mknod(). It keeps refreshing this info every X seconds. I will let DHT guys comment a bit more about this. One more thing to check is if we can have just one implementation that satisfied everyone's requirements. i.e. move out this functionality from DHT to this xlator or, move the functionality of this xlator into DHT.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 13, 2017 at 8:18 AM, Taehwa Lee <span dir="ltr"><<a href="mailto:alghost.lee@gmail.com" target="_blank">alghost.lee@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 style="word-wrap:break-word"><div>Hi all, </div><div><br></div><div>I’ve been developing a xlator that create is rejected when used capacity of a volume higher than threshold.</div><div><br></div><div><br></div><div>the reason why I’m doing is that I got problems when LV is used fully.</div><div><br></div><div>this patch is in the middle of develop.</div><div><br></div><div>just I want to know whether my approach is pretty correct to satisfy my requirement.</div><div><br></div><div>so, when you guys have a little spare time, please review my patch and tell me WHATEVER you’re thinking.</div><div><br></div><div><br></div><div>and If you guys think that it is useful for glusterfs, I’m gonna do process to merge into glusterfs.</div><div><br></div><div><br></div><div>thanks in advance</div><div><br></div><div><br></div></div><br><div style="word-wrap:break-word"><br><div>
<div style="word-wrap:break-word"><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br>------------------------------<wbr>-----------<br>Taehwa Lee<br>Gluesys Co.,Ltd.<br><a href="mailto:alghost.lee@gmail.com" target="_blank">alghost.lee@gmail.com</a><br>+82-10-3420-6114, +82-70-8785-6591<br>------------------------------<wbr>-----------</div></div>
</div>
<br></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><br clear="all"><br>-- <br><div class="m_8036603510263190773m_746561717897587908gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div>
</div></div></div></blockquote></div><br></div></blockquote></div></div></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div class="m_8036603510263190773gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</font></span></div></div>
</blockquote></div><br></div></div>