Any update?
On Fri, Oct 13, 2017 at 1:14 PM, Amudhan P wrote:
> any update?.
>
> why is it marked bad?
>
> Any way to find out what happened to the file?
>
>
> On Tue, Oct 3, 2017 at 12:44 PM, Amudhan P wrote:
>
>>
>> my volume is distributed disperse volume 8+2 EC.
>> file1 and file2 are diffe
any update?.
why is it marked bad?
Any way to find out what happened to the file?
On Tue, Oct 3, 2017 at 12:44 PM, Amudhan P wrote:
>
> my volume is distributed disperse volume 8+2 EC.
> file1 and file2 are different files lying in same brick. I am able to read
> the file from mount point wit
my volume is distributed disperse volume 8+2 EC.
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.
my question is "file1" sha256 value matches bitrot signature v
Hi Amudhan,
Sorry for the late response as I was busy with other things. You are right
bitrot uses sha256 for checksum.
If file-1, file-2 are marked bad, the I/O should be errored out with EIO.
If that is not happening, we need
to look further into it. But what's the file contents of file-1 and fi
resending mail.
On Fri, Sep 22, 2017 at 5:30 PM, Amudhan P wrote:
> ok, from bitrot code I figured out gluster using sha256 hashing algo.
>
>
> Now coming to the problem, during scrub run in my cluster some of my files
> were marked as bad in few set of nodes.
> I just wanted to confirm bad file
ok, from bitrot code I figured out gluster using sha256 hashing algo.
Now coming to the problem, during scrub run in my cluster some of my files
were marked as bad in few set of nodes.
I just wanted to confirm bad file. so, I have used "sha256sum" tool in
Linux to manually get file hash.
here is
