<div dir="ltr">Yes it could as depending on number of bricks there might be too many brick ops involved. This is the reason we introduced --timeout option in CLI which can be used to have a larger time out value. However this fix is available from release-3.9 onwards. <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 24, 2017 at 3:54 PM, lejeczek <span dir="ltr"><<a href="mailto:peljasz@yahoo.co.uk" target="_blank">peljasz@yahoo.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi fellas<br>
<br>
would you know what could be the problem with: vol status detail times out always?<br>
After I did above I had to restart glusterd on the peer which had the command issued.<br>
I run 3.8.14. Everything seems to work a ok.<br>
<br>
many thanks<br>
L.<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-users</a><br>
</blockquote></div><br></div>