<div dir="ltr">resending mail.<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 22, 2017 at 5:30 PM, Amudhan P <span dir="ltr"><<a href="mailto:amudhan83@gmail.com" target="_blank">amudhan83@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">ok, from bitrot code I figured out gluster using sha256 hashing algo.<div><br></div><div><div><br></div><div>Now coming to the problem, during scrub run in my cluster some of my files were marked as bad in few set of nodes. </div><div>I just wanted to confirm bad file. so, I have used "sha256sum" tool in Linux to manually get file hash.</div></div><div><br></div><div>here is the result.</div><div><br></div><div><div>file-1, file-2 marked as bad by scrub and file-3 is healthy.</div><div><br></div><div><div>file-1 sha256 and bitrot signature value matches but still it's been marked as bad.</div><div><br></div><div>file-2 sha256 and bitrot signature value don't match, could be a victim of bitrot or bitflip.file is still readable without any issue and no errors found in the drive.</div><div><br></div><div>file-3 sha256 and bitrot signature matches and healthy.</div></div><div><br></div><div><br></div><div>file-1 output from </div><div><br></div><div>"sha256sum" = "<wbr>71eada9352b1352aaef0f806d3d561<wbr>768ce2df905ded1668f665e06eca2d<wbr>0bd4"</div><div><br></div><div><br></div><div>"getfattr -m. -e hex -d "</div><div># file: file-1</div><div>trusted.bit-rot.bad-file=<wbr>0x3100</div><div>trusted.bit-rot.signature=<wbr>0x01020000000000000071eada9352<wbr>b1352aaef0f806d3d561768ce2df90<wbr>5ded1668f665e06eca2d0bd4</div><div>trusted.bit-rot.version=<wbr>0x020000000000000058e4f3b40006<wbr>793d</div><div>trusted.ec.config=<wbr>0x0000080a02000200</div><div>trusted.ec.dirty=<wbr>0x0000000000000000000000000000<wbr>0000</div><div>trusted.ec.size=<wbr>0x0000000718996701</div><div>trusted.ec.version=<wbr>0x0000000000038c4c000000000003<wbr>8c4d</div><div>trusted.gfid=<wbr>0xf078a24134fe4f9bb953eca8c28d<wbr>ea9a</div><div><br></div><div>output scrub log:</div><div>[2017-09-02 13:02:20.311160] A [MSGID: 118023] [bit-rot-scrub.c:244:bitd_<wbr>compare_ckum] 0-qubevaultdr-bit-rot-0: CORRUPTION DETECTED: Object /file-1 {Brick: /media/disk16/brick16 | GFID: f078a241-34fe-4f9b-b953-<wbr>eca8c28dea9a}</div><div>[2017-09-02 13:02:20.311579] A [MSGID: 118024] [bit-rot-scrub.c:264:bitd_<wbr>compare_ckum] 0-qubevaultdr-bit-rot-0: Marking /file-1 [GFID: f078a241-34fe-4f9b-b953-<wbr>eca8c28dea9a | Brick: /media/disk16/brick16] as corrupted..</div><div><br></div><div>file-2 output from </div><div><br></div><div>"sha256sum" = "<wbr>c41ef9c81faed4f3e6010ea67984c3<wbr>cfefd842f98ee342939151f9250972<wbr>dcda"</div><div><br></div><div><br></div><div>"getfattr -m. -e hex -d "</div><div># file: file-2</div><div>trusted.bit-rot.bad-file=<wbr>0x3100</div><div>trusted.bit-rot.signature=<wbr>0x0102000000000000009162cb17d4<wbr>f0bee676fcb7830c5286d05b8e8940<wbr>d14f3d117cb90b7b1defc129</div><div>trusted.bit-rot.version=<wbr>0x020000000000000058e4f3b40001<wbr>9bb2</div><div>trusted.ec.config=<wbr>0x0000080a02000200</div><div>trusted.ec.dirty=<wbr>0x0000000000000000000000000000<wbr>0000</div><div>trusted.ec.size=<wbr>0x00000000403433f6</div><div>trusted.ec.version=<wbr>0x000000000000201a000000000000<wbr>201b</div><div>trusted.gfid=<wbr>0xa50012b0a632477c99232313928d<wbr>239a</div><div><br></div><div>output scrub log:</div><div>[2017-09-02 05:18:14.003156] A [MSGID: 118023] [bit-rot-scrub.c:244:bitd_<wbr>compare_ckum] 0-qubevaultdr-bit-rot-0: CORRUPTION DETECTED: Object /file-2 {Brick: /media/disk13/brick13 | GFID: a50012b0-a632-477c-9923-<wbr>2313928d239a}</div><div>[2017-09-02 05:18:14.006629] A [MSGID: 118024] [bit-rot-scrub.c:264:bitd_<wbr>compare_ckum] 0-qubevaultdr-bit-rot-0: Marking /file-2 [GFID: a50012b0-a632-477c-9923-<wbr>2313928d239a | Brick: /media/disk13/brick13] as corrupted..</div><div><br></div><div><br></div><div>file-3 output from </div><div><br></div><div>"sha256sum" = "<wbr>a590735b3c8936cc7ca9835128a19c<wbr>38a3f79c8fd53fddc031a9349b7e27<wbr>3f27"</div><div><br></div><div><br></div><div>"getfattr -m. -e hex -d "</div><div># file: file-3</div><div>trusted.bit-rot.signature=<wbr>0x010200000000000000a590735b3c<wbr>8936cc7ca9835128a19c38a3f79c8f<wbr>d53fddc031a9349b7e273f27</div><div>trusted.bit-rot.version=<wbr>0x020000000000000058e4f3b40001<wbr>9bb2</div><div>trusted.ec.config=<wbr>0x0000080a02000200</div><div>trusted.ec.dirty=<wbr>0x0000000000000000000000000000<wbr>0000</div><div>trusted.ec.size=<wbr>0x000000003530fc96</div><div>trusted.ec.version=<wbr>0x0000000000001a98000000000000<wbr>1a99</div><div>trusted.gfid=<wbr>0x10d8920e42cd42cf9448b8bf3941<wbr>c192</div></div><div><br></div><div><br></div><div><br></div><div>most of the bitrot bad files are in the set of new nodes and data were uploaded using gluster 3.10.1. no drive issues are any kind of error msgs in logs.<br></div><div><br></div><div>what could be gone wrong?</div><div><br></div><div>regards</div><span class="HOEnZb"><font color="#888888"><div>Amudhan</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 21, 2017 at 1:23 PM, Amudhan P <span dir="ltr"><<a href="mailto:amudhan83@gmail.com" target="_blank">amudhan83@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I have a file in my brick which was signed by bitrot and latter when running scrub it was marked as bad.</div><div><br></div><div>Now, I want to verify file again manually. just to clarify my doubt</div><div><br></div><div>how can I do this?</div><div><br></div><div><br></div><div>regards</div><span class="m_-318158717141031202HOEnZb"><font color="#888888"><div>Amudhan</div></font></span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>