search for: 0x00000000000000000000000000000000

...file: file-1 > trusted.bit-rot.bad-file=0x3100 > trusted.bit-rot.signature=0x01020000000000000071eada9352 > b1352aaef0f806d3d561768ce2df905ded1668f665e06eca2d0bd4 > trusted.bit-rot.version=0x020000000000000058e4f3b40006793d > trusted.ec.config=0x0000080a02000200 > trusted.ec.dirty=0x00000000000000000000000000000000 > trusted.ec.size=0x0000000718996701 > trusted.ec.version=0x0000000000038c4c0000000000038c4d > trusted.gfid=0xf078a24134fe4f9bb953eca8c28dea9a > > output scrub log: > [2017-09-02 13:02:20.311160] A [MSGID: 118023] [bit-rot-scrub.c:244:bitd_compare_ckum] > 0-qubevaultdr-bit-rot-...

...etfattr -m. -e hex -d " # file: 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 output scrub log: [2017-09-02 13:02:20.311160] A [MSGID: 118023] [bit-rot-scrub.c:244:bitd_compare_ckum] 0-qubevaultdr-bit-rot-0: CORRUPTION DETECTED: Object /fi...

Hi, I have a file in my brick which was signed by bitrot and latter when running scrub it was marked as bad. Now, I want to verify file again manually. just to clarify my doubt how can I do this? regards Amudhan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170921/f69ff7be/attachment.html>

...le=0x3100 >>> trusted.bit-rot.signature=0x01020000000000000071eada9352b135 >>> 2aaef0f806d3d561768ce2df905ded1668f665e06eca2d0bd4 >>> trusted.bit-rot.version=0x020000000000000058e4f3b40006793d >>> trusted.ec.config=0x0000080a02000200 >>> trusted.ec.dirty=0x00000000000000000000000000000000 >>> trusted.ec.size=0x0000000718996701 >>> trusted.ec.version=0x0000000000038c4c0000000000038c4d >>> trusted.gfid=0xf078a24134fe4f9bb953eca8c28dea9a >>> >>> output scrub log: >>> [2017-09-02 13:02:20.311160] A [MSGID: 118023] >>> [bit-r...

...usted.bit-rot.bad-file=0x3100 >> trusted.bit-rot.signature=0x01020000000000000071eada9352b135 >> 2aaef0f806d3d561768ce2df905ded1668f665e06eca2d0bd4 >> trusted.bit-rot.version=0x020000000000000058e4f3b40006793d >> trusted.ec.config=0x0000080a02000200 >> trusted.ec.dirty=0x00000000000000000000000000000000 >> trusted.ec.size=0x0000000718996701 >> trusted.ec.version=0x0000000000038c4c0000000000038c4d >> trusted.gfid=0xf078a24134fe4f9bb953eca8c28dea9a >> >> output scrub log: >> [2017-09-02 13:02:20.311160] A [MSGID: 118023] >> [bit-rot-scrub.c:244:bitd_compare_...

...it-rot.signature=0x01020000000000000071eada9352b135 >>>>> 2aaef0f806d3d561768ce2df905ded1668f665e06eca2d0bd4 >>>>> trusted.bit-rot.version=0x020000000000000058e4f3b40006793d >>>>> trusted.ec.config=0x0000080a02000200 >>>>> trusted.ec.dirty=0x00000000000000000000000000000000 >>>>> trusted.ec.size=0x0000000718996701 >>>>> trusted.ec.version=0x0000000000038c4c0000000000038c4d >>>>> trusted.gfid=0xf078a24134fe4f9bb953eca8c28dea9a >>>>> >>>>> output scrub log: >>>>> [2017-09-02 13:02:...

...Warning on the client mount) I ran getfattr -m . -d -e hex <brick>/<file> across all servers in the cluster and 'trusted.ec.dirty' attr is non-zero on all files which don't heal. Is it normal? Any way to correct it? It's my understanding it should be trusted.ec.dirty=0x00000000000000000000000000000000 for 'good' files. Out of 12 copies of the files, 11 have the same non-zero value (0x00000000001115920000000000000000), and 12th file has a different non-zero value. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipe...

http://bugzilla.mindrot.org/show_bug.cgi?id=748 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |japs at adm.ku.dk ------- Additional Comments From dtucker at zip.com.au 2004-03-22 22:46 ------- *** Bug 816 has been marked as a

Hi, I have been playing with Altivec, and I rewrote a couple of the routines in assembly. Looking at the archives, I noticed that there may already be some effort on this. Anyways... Right now, I have two routines working. They need to be cleaned up, made relocatable, and documented; otherwise, they seem to work fairly well. I see an overall ~27% speed improvement when encoding with the