The problem was that I was running the gluster server in a docker container which only had 9.9G available at root, instead I am mounting the "brick" from the host into the container and that works as expected.
On Mon, Nov 3, 2014 at 9:08 AM, Kingsley Tart - Barritel <kingsley.tart@xxxxxxxxxxxx> wrote:
I found that when I tested, the amount of space reported was dependant
on the free space on the smallest brick.
How much free space do you have on your bricks?
Cheers,
Kingsley.
> _______________________________________________
On Mon, 2014-11-03 at 07:58 -0500, craig w wrote:
> Using gluster 3.5.2, I created a volume and started it.
>
>
> On a host, I mounted it:
>
>
> mount -t glusterfs -o direct-io-mode=disable
> <ip>:/myvolume /var/data
>
>
> When I do a "df -h" on the host I see that the filesystem "/var/data"
> is only 9.9G, how can I increase this as I'd like to put more than
> 9.9GB of data into it.
>
> Thanks.
>
> --
> https://github.com/mindscratch
> https://www.google.com/+CraigWickesser
>
> https://twitter.com/mind_scratch
>
> https://twitter.com/craig_links
>
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
--
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
