I reply to myself.
did a memtest on the server.
the bios was ECC enabled, but the memory was not capable.
memtest return once a mistake.
idem est : bad crc.
my conclusion : don't test moosefs on too old hardware :-)
jyc wrote:
> Hi everyone,
>
> i have a cluster with 4 chunkservers with moosefs.
> on one server, i got this problem :
>
> i had many filesystem check info with no problem.
> but now, i get one chunk with a goal of one, and a valid copie of zero.
>
> in the log, I get :
>
> but now Jun 28 14:53:39 read_block_from_chunk:
> file:/opt/ba1d3/mfs/2B/chunk_000000000000962B_00000001.mfs - crc error
>
> but the file was written five days before :
>
> mfs mfs 65M jun 23 03:04
> /opt/ba1d3/mfs/2B/chunk_000000000000962B_00000001.mfs
>
> can you explain me why this chunk was correct for five days, and now it
> seems that it is not ?
>
> by the way, what process do the crc ?
> is it the mfschunkserver that check it (I think it must be) where is
> stored the "correct" crc ? in the mfsmaster process/file ?
>
> (on this server, i got 4 hdds, all with xfs filesystem. i changed the
> motherboard. system is still the same after changing the motherboard.
> kernel 2.6.26-2-686 )
>
> any clue ?
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>
>
|
