<div dir="ltr">Any update?<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 13, 2017 at 1:14 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">any update?. <div><br><div>why is it marked bad? </div><div><br></div><div>Any way to find out what happened to the file?</div><div><div class="h5"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 3, 2017 at 12:44 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"><div class="gmail_extra"> </div><div class="gmail_extra">my volume is distributed disperse volume 8+2 EC. </div><div class="gmail_extra">file1 and file2 are different files lying in same brick. I am able to read the file from mount point without any issue because of EC it reads rest of the available blocks in other nodes.</div><div class="gmail_extra"><br></div><div class="gmail_extra">my question is "file1" sha256 value matches bitrot signature value but still, it is also marked as bad by scrubber daemon. why is that?</div><div><div class="m_7100855472180407908h5"><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 29, 2017 at 12:52 PM, Kotresh Hiremath Ravishankar <span dir="ltr"><<a href="mailto:khiremat@redhat.com" target="_blank">khiremat@redhat.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"><div><div>Hi Amudhan,<br><br></div>Sorry for the late response as I was busy with other things. You are right bitrot uses sha256 for checksum.<br></div><div>If file-1, file-2 are marked bad, the I/O should be errored out with EIO. If that is not happening, we need<br></div><div>to look further into it. But what's the file contents of file-1 and file-2 on the replica bricks ? Are they<br></div><div>matching ?<br><br></div><div>Thanks and Regards,<br></div><div>Kotresh HR<br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_7100855472180407908m_1691881501526693628m_4912489624036599018h5">On Mon, Sep 25, 2017 at 4:19 PM, Amudhan P <span dir="ltr"><<a href="mailto:amudhan83@gmail.com" target="_blank">amudhan83@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_7100855472180407908m_1691881501526693628m_4912489624036599018h5"><div dir="ltr">resending mail.<div><div class="m_7100855472180407908m_1691881501526693628m_4912489624036599018m_-3024623946723252849h5"><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" = "71eada9352b1352aaef0f806d3d56<wbr>1768ce2df905ded1668f665e06eca2<wbr>d0bd4"</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=0x310<wbr>0</div><div>trusted.bit-rot.signature=0x01<wbr>020000000000000071eada9352b135<wbr>2aaef0f806d3d561768ce2df905ded<wbr>1668f665e06eca2d0bd4</div><div>trusted.bit-rot.version=0x0200<wbr>00000000000058e4f3b40006793d</div><div>trusted.ec.config=0x0000080a02<wbr>000200</div><div>trusted.ec.dirty=0x00000000000<wbr>000000000000000000000</div><div>trusted.ec.size=0x000000071899<wbr>6701</div><div>trusted.ec.version=0x000000000<wbr>0038c4c0000000000038c4d</div><div>trusted.gfid=0xf078a24134fe4f9<wbr>bb953eca8c28dea9a</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_comp<wbr>are_ckum] 0-qubevaultdr-bit-rot-0: CORRUPTION DETECTED: Object /file-1 {Brick: /media/disk16/brick16 | GFID: f078a241-34fe-4f9b-b953-eca8c2<wbr>8dea9a}</div><div>[2017-09-02 13:02:20.311579] A [MSGID: 118024] [bit-rot-scrub.c:264:bitd_comp<wbr>are_ckum] 0-qubevaultdr-bit-rot-0: Marking /file-1 [GFID: f078a241-34fe-4f9b-b953-eca8c2<wbr>8dea9a | Brick: /media/disk16/brick16] as corrupted..</div><div><br></div><div>file-2 output from </div><div><br></div><div>"sha256sum" = "c41ef9c81faed4f3e6010ea67984c<wbr>3cfefd842f98ee342939151f925097<wbr>2dcda"</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=0x310<wbr>0</div><div>trusted.bit-rot.signature=0x01<wbr>02000000000000009162cb17d4f0be<wbr>e676fcb7830c5286d05b8e8940d14f<wbr>3d117cb90b7b1defc129</div><div>trusted.bit-rot.version=0x0200<wbr>00000000000058e4f3b400019bb2</div><div>trusted.ec.config=0x0000080a02<wbr>000200</div><div>trusted.ec.dirty=0x00000000000<wbr>000000000000000000000</div><div>trusted.ec.size=0x000000004034<wbr>33f6</div><div>trusted.ec.version=0x000000000<wbr>000201a000000000000201b</div><div>trusted.gfid=0xa50012b0a632477<wbr>c99232313928d239a</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_comp<wbr>are_ckum] 0-qubevaultdr-bit-rot-0: CORRUPTION DETECTED: Object /file-2 {Brick: /media/disk13/brick13 | GFID: a50012b0-a632-477c-9923-231392<wbr>8d239a}</div><div>[2017-09-02 05:18:14.006629] A [MSGID: 118024] [bit-rot-scrub.c:264:bitd_comp<wbr>are_ckum] 0-qubevaultdr-bit-rot-0: Marking /file-2 [GFID: a50012b0-a632-477c-9923-231392<wbr>8d239a | Brick: /media/disk13/brick13] as corrupted..</div><div><br></div><div><br></div><div>file-3 output from </div><div><br></div><div>"sha256sum" = "a590735b3c8936cc7ca9835128a19<wbr>c38a3f79c8fd53fddc031a9349b7e2<wbr>73f27"</div><div><br></div><div><br></div><div>"getfattr -m. -e hex -d "</div><div># file: file-3</div><div>trusted.bit-rot.signature=0x01<wbr>0200000000000000a590735b3c8936<wbr>cc7ca9835128a19c38a3f79c8fd53f<wbr>ddc031a9349b7e273f27</div><div>trusted.bit-rot.version=0x0200<wbr>00000000000058e4f3b400019bb2</div><div>trusted.ec.config=0x0000080a02<wbr>000200</div><div>trusted.ec.dirty=0x00000000000<wbr>000000000000000000000</div><div>trusted.ec.size=0x000000003530<wbr>fc96</div><div>trusted.ec.version=0x000000000<wbr>0001a980000000000001a99</div><div>trusted.gfid=0x10d8920e42cd42c<wbr>f9448b8bf3941c192</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="m_7100855472180407908m_1691881501526693628m_4912489624036599018m_-3024623946723252849m_7431365665901166228HOEnZb"><font color="#888888"><div>Amudhan</div></font></span></div><div class="m_7100855472180407908m_1691881501526693628m_4912489624036599018m_-3024623946723252849m_7431365665901166228HOEnZb"><div class="m_7100855472180407908m_1691881501526693628m_4912489624036599018m_-3024623946723252849m_7431365665901166228h5"><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_7100855472180407908m_1691881501526693628m_4912489624036599018m_-3024623946723252849m_7431365665901166228m_-318158717141031202HOEnZb"><font color="#888888"><div>Amudhan</div></font></span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div></div>
<br></div></div><span>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-users</a><br></span></blockquote></div><span class="m_7100855472180407908m_1691881501526693628m_4912489624036599018HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div class="m_7100855472180407908m_1691881501526693628m_4912489624036599018m_-3024623946723252849gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Thanks and Regards,<br></div>Kotresh H R<br></div></div>
</font></span></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div></div></div></div></div></div>
</blockquote></div><br></div></div>