Hello Raghavendra,
I can not give you the output of the gluster commands because I repaired
the system already. But beside of this this errors occurs randomly. I am
sure that only one copy of the file was corrupted because it is part of a
test and I corrupt one copy of the file manually on brick l
Hi David,
Do you have any bricks down? Can you please share the output of the
following commands and also the logs of the server and the client nodes?
1) gluster volume info
2) gluster volume status
3) gluster volume bitrot scrub status
Few more questions
1) How many copies of the file were co
Hello Amar,
sounds good. Until now this patch is only merged into master. I think it
should be part of the next v5.x patch release!
Regards
David
Am Mo., 4. Feb. 2019 um 09:58 Uhr schrieb Amar Tumballi Suryanarayan <
atumb...@redhat.com>:
> Hi David,
>
> I guess https://review.gluster.org/#/c/gl
Hi David,
I guess https://review.gluster.org/#/c/glusterfs/+/21996/ helps to fix the
issue. I will leave it to Raghavendra Bhat to reconfirm.
Regards,
Amar
On Fri, Feb 1, 2019 at 8:45 PM David Spisla wrote:
> Hello Gluster Community,
> I have got a 4 Node Cluster with a Replica 4 Volume, so ea
Hello Gluster Community,
I have got a 4 Node Cluster with a Replica 4 Volume, so each node has a
brick with a copy of a file. Now I tried out the bitrot functionality and
corrupt the copy on the brick of node1. After this I scrub ondemand and the
file is marked correctly as corrupted.
No I try to
