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.
I'm running a distributed / replicated volume, 2 boxes with 3 bricks each, gluster 3.12.1
Thanks
-Tom
On Tue, Dec 19, 2017 at 4:24 PM, Teknologeek Teknologeek <teknologeek06@xxxxxxxxx> wrote:
I need some help to understand what's going on as i can't delete the volume and recreate it from scratch.When browsing the data, they seem to be ok tho."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.I have a glusterfs setup with distributed disperse volumes 5 * ( 4 + 2 ).After a server crash, "gluster peer status" reports all peers as connected.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
