Gluster users - Oct 2016 - bitrot log messages

Hi,

Redhat documentation says that things will get logged to bitd.log, and
scrub.log.  These files are pretty big - even when we only take the ? E ? log
level lines.

https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/chap-Detecting_Data_Corruption.html
<https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/chap-Detecting_Data_Corruption.html>

Anyone know which particular message patterns we should be actively looking for
to detect bitrot?

Thanks,
Jackie
-- 
 

The information in this email is confidential and may be legally 
privileged. It is intended solely for the addressee. Access to this email 
by anyone else is unauthorized. If you are not the intended recipient, any 
disclosure, copying, distribution or any action taken or omitted to be 
taken in reliance on it, is prohibited and may be unlawful.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20161025/37e95de1/attachment.html>

Hi Jackie,

"gluster vol bitrot <volname> status" should show the corrupted
files gfid.
If you want to get the info from logs, it will be logged as below.

[2016-10-26 05:21:20.767774] A [MSGID: 118023]
[bit-rot-scrub.c:246:bitd_compare_ckum] 0-master-bit-rot-0: CORRUPTION DETECTED:
Object /dir1/file1 {Brick: /bricks/brick1/b10 | GFID:
b912c776-7253-4418-a35f-a37661d673b6}
[2016-10-26 05:21:20.770294] A [MSGID: 118024]
[bit-rot-scrub.c:266:bitd_compare_ckum] 0-master-bit-rot-0: Marking /dir1/file1
[GFID: b912c776-7253-4418-a35f-a37661d673b6 | Brick: /bricks/brick1/b10] as
corrupted..


Thanks and Regards,
Kotresh H R

----- Original Message -----
> From: "Jackie Tung" <jackie at drive.ai>
> To: gluster-users at gluster.org
> Sent: Wednesday, October 26, 2016 2:14:28 AM
> Subject: [Gluster-users] bitrot log messages
> 
> Hi,
> 
> Redhat documentation says that things will get logged to bitd.log, and
> scrub.log. These files are pretty big - even when we only take the ? E ?
log
> level lines.
> 
>
https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/chap-Detecting_Data_Corruption.html
> 
> Anyone know which particular message patterns we should be actively looking
> for to detect bitrot?
> 
> Thanks,
> Jackie
> 
> 
> 
> The information in this email is confidential and may be legally
privileged.
> It is intended solely for the addressee. Access to this email by anyone
else
> is unauthorized. If you are not the intended recipient, any disclosure,
> copying, distribution or any action taken or omitted to be taken in
reliance
> on it, is prohibited and may be unlawful.
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users