<div dir="ltr">I'm seeing a similar issue. It appears that df on the client is reporting the *brick* size instead of the total pool size. I think that this started happening after one of my servers crashed due to a hardware issue.<div><br></div><div>I'm running a distributed / replicated volume, 2 boxes with 3 bricks each, gluster 3.12.1</div><div><br></div><div>Thanks</div><div>-Tom</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 19, 2017 at 4:24 PM, Teknologeek Teknologeek <span dir="ltr"><<a href="mailto:teknologeek06@gmail.com" target="_blank">teknologeek06@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>I have a glusterfs setup with distributed disperse volumes 5 * ( 4 + 2 ).<br><br></div>After a server crash, "gluster peer status" reports all peers as connected.<br><br></div>"gluster volume status detail" shows that all bricks are up and running with the right size, but when I use df from a client mount point, the size displayed is about 1/6 of the total size.<br><br></div>When browsing the data, they seem to be ok tho.<br><br></div>I need some help to understand what's going on as i can't delete the volume and recreate it from scratch.<br></div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>