for email, fastest to do would be: update to latest 3.12 on all nodes, make
sure they all communicate properly and create new volume, move data there.
try using volume options from here:
https://lists.gluster.org/pipermail/gluster-users/2018-October/035077.html
-v
On Fri, Oct 12, 2018 at 1:50
Well,
It's been doing this for weeks, at least. I hope that by the time the
healing of a simple file like this one would be over.
Besides, the contents of the "cur" directory must also be under healing,
but it takes s long it's strange.
Hoggins!
Le 10/10/2018 à 07:05, Vlad Kopylov a
isn't it trying to heal your dovecot-uidlist? try updating, restarting and
initiating heal again
-v
On Sun, Oct 7, 2018 at 12:54 PM Hoggins! wrote:
> Hello list,
>
> My Gluster cluster has a condition, I'd like to know how to cure it.
>
> The setup: two bricks, replicated, with an arbiter.
>
Hello list,
My Gluster cluster has a condition, I'd like to know how to cure it.
The setup: two bricks, replicated, with an arbiter.
On brick 1, the /var/log/glusterfs/glustershd.log is quite empty, not
much activity, everything looks fine.
On brick 2, /var/log/glusterfs/glustershd.log shows a
