;
> =
>
>
> Thanks and Regards,
> Kotresh H R
>
> - Original Message -
>> From: "Jackie Tung" <jac...@drive.ai>
>> To: "Kotresh Hiremath Ravishankar" <khire...@redhat.com>
To: "Kotresh Hiremath Ravishankar" <khire...@redhat.com>
> Cc: gluster-users@gluster.org
> Sent: Wednesday, October 26, 2016 8:34:07 PM
> Subject: Re: [Gluster-users] bitrot log messages
>
> That’s great, thank you! We plan to automatically look for these signs.
>
> For
quot; <jac...@drive.ai>
>> Cc: gluster-users@gluster.org
>> Sent: Wednesday, October 26, 2016 10:53:50 AM
>> Subject: Re: [Gluster-users] bitrot log messages
>>
>> Hi Jackie,
>>
>> "gluster vol bitrot status" should show the corrupted fi
ve.ai>
> Cc: gluster-users@gluster.org
> Sent: Wednesday, October 26, 2016 10:53:50 AM
> Subject: Re: [Gluster-users] bitrot log messages
>
> Hi Jackie,
>
> "gluster vol bitrot status" should show the corrupted files gfid.
> If you want to get the info from logs, it w
.
Thanks and Regards,
Kotresh H R
- Original Message -
> From: "Jackie Tung" <jac...@drive.ai>
> To: gluster-users@gluster.org
> Sent: Wednesday, October 26, 2016 2:14:28 AM
> Subject: [Gluster-users] bitrot log messages
>
> Hi,
>
> Redhat document
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
