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.
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.