[Bugs] [Bug 1506108] New: bitrot scrub marking a good file as bad

[bugzilla at redhat.com]

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

            Bug ID: 1506108
           Summary: bitrot scrub marking a good file as bad
           Product: GlusterFS
           Version: 3.10
         Component: bitrot
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: amudhan83 at gmail.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem:
scrub daemon marked a file as bad, but when I compare file manually using
sha256sum utility result matches bit-rot-signature value in xattr of the file.

Version-Release number of selected component (if applicable):
3.10.1

How reproducible:
currently files are marked bad and due to srucb instability i have paused scrub
daemon. So, I couldn't reproduce it in my working setup.

In test setup also couldn't reproduce.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
xattr output of file from brick which is marked as bad. assuming file name as
"file-1"

getfattr -m. -e hex -d file-1

trusted.bit-rot.bad-file=0x3100
trusted.bit-rot.signature=0x01020000000000000071eada9352b1352aaef0f806d3d561768ce2df905ded1668f665e06eca2d0bd4
trusted.bit-rot.version=0x020000000000000058e4f3b40006793d
trusted.ec.config=0x0000080a02000200
trusted.ec.dirty=0x00000000000000000000000000000000
trusted.ec.size=0x0000000718996701
trusted.ec.version=0x0000000000038c4c0000000000038c4d
trusted.gfid=0xf078a24134fe4f9bb953eca8c28dea9a


same file running with "sha256sum" util in Linux

sha256sum file-1

71eada9352b1352aaef0f806d3d561768ce2df905ded1668f665e06eca2d0bd4   file-1

output result matches bit-rot signature value but still, it is marked as bad
like this I have more 10-15 files marked as bad.

-- 
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.