[Bugs] [Bug 1210687] New: BitRot :- If scrubber finds bad file then it should log as a 'Error' in log not 'Warning'

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1210687

            Bug ID: 1210687
           Summary: BitRot :- If scrubber finds bad file then it should
                    log as a 'Error' in log not 'Warning'
           Product: GlusterFS
           Version: mainline
         Component: bitrot
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: racpatel at redhat.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem:
=======================
Scrubber log should report 'bad' file detection as Error in log.


Version-Release number of selected component (if applicable):
=============================================================
3.7dev-0.952.gita7f1d08.el6.x86_64

How reproducible:
=================
always

Steps to Reproduce:
===================
1. create and mount volume.
2. enable bitrot
3. create file
4. modify file from backend(not from mount)
5. check scrub log

Actual Result:-
===============
[2015-04-09 09:14:41.002867] W [bit-rot-scrub.c:208:bitd_compare_ckum]
0-bit-rot: Object checksumsum mismatch: f9 [GFID:
c2ca6098-ab30-4d9c-9027-df491e07c0f7]
[2015-04-09 09:14:41.002920] I [bit-rot-scrub.c:226:bitd_compare_ckum]
0-bit-rot: Marking f9 [GFID: c2ca6098-ab30-4d9c-9027-df491e07c0f7] as
corrupted..

Expect Result:-
===============
Object Checksum mismatch should come as 'Error' not warning

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.