Dear All,
I figured it out, it appeared to be the exact same issue as described
here;
https://lists.gluster.org/pipermail/gluster-users/2018-March/033785.html
Another subvolume also had the shard file, only were all 0 bytes and had
the dht.linkto
for reference;
[root@lease-04 ovirt-backbone-2]# g
Hi,
The "Server busy" error is typically returned in one of two scenarios:
* The server really is busy processing multiple parallel requests
* Heketi needs a block hosting volume to satisfy a block volume request but
the only block hosting volumes are pending (still being created).
In your case
Hi all,
I'm looking to update Samba from fasttrack, but I only still se 4.8.3 and yum
is not wanting to update. The test build is also showing 4.8.3.
Thank you!
From: gluster-users-boun...@gluster.org On
Behalf Of Matt Waymack
Sent: Sunday, December 16, 2018 1:55 PM
To: Diego Remolina
Cc:
Hi Matt,
The update is slightly different, has the .1 at the end:
Fast-track -> samba-4.8.3-4.el7.0.1.x86_64.rpm
vs general -> samba-4.8.3-4.el7.x86_64
I think these are built, but not pushed to fasttrack repo until they
get feedback the packages are good. So you may need to use wget to
downloa
I have one volume that has 85 pending entries in healing and two more
volumes with 58,854 entries in healing pending. These numbers are from
the volume heal info summary command. They have stayed constant for two
days now. I've read the gluster docs and many more. The Gluster docs
just give
Assuming your bricks are up... yes, the heal count should be decreasing.
There is/was a bug wherein self-heal would stop healing but would still be
running. I don't know whether your version is affected, but the remedy is
to just restart the self-heal daemon.
Force start one of the volumes that ha
