Hi,
Given the numerous problems we've had with setting up gluster for VM
hosting at the start, we've been staying with 3.7.15, which was the
first version to work properly.
However the repo for 3.7.15 is now down, so we've decided to give
3.12.9 a try. Unfortunatly, a few days ago, one of our
hi guys
I've had two replicas volume, added third brick and now I see hundred
thousand files to heal, interestingly though only on two bricks that
already constituted the volume.
Volume prior to expansion was, according to gluster, okey and when I
added third brick it immediately started
Hi,
That's normal, the heal is how it syncs the files to the new bricks.
And yes, the heal shows on the sources, not on the destination, which is
a bit weird but that's just how it is :)
On Mon, Jun 11, 2018 at 10:25:08AM +0100, lejeczek wrote:
> hi guys
>
> I've had two replicas volume, added
Hi
Since I have updated our gluster server and client to latest version
3.12.9-1, I am having this issue of gluster getting unmounted from client
very regularly. It was not a problem before update.
Its a distributed file system with no replication. We have seven servers
totaling around 480TB
On Mon, Jun 11, 2018 at 8:50 AM, mohammad kashif
wrote:
> Hi
>
> Since I have updated our gluster server and client to latest version
> 3.12.9-1, I am having this issue of gluster getting unmounted from client
> very regularly. It was not a problem before update.
>
> Its a distributed file
Hi,
I would like to understand how gluster works better than I do know and in
particular the architecture.
So I have a test configuration of 6 desktops, each has 2 x 1TB disks in a
raid 0 on an esata channel.
What I would like to do I think is a,
*Distributed-Replicated volume*
a) have 1 and
