Re: [MooseFS-Users] Multiple CRC failures

[Jakub Kruszona-Z. <jak...@ge...>]

> On 9 Jun, 2018, at 12:20, Gandalf Corvotempesta <gan...@gm...> wrote:
> 
> Last crc failure i've seen for the "rotted" file is here:
> 
> Jun  8 22:03:36 cs02 mfschunkserver[22075]: chunk_readcrc:
> file:/mnt/chunks/chunk0/chunk//01/chunk_00000000006639E9_00000001.mfs
> - read error: Success (errno=0)
> Jun  8 22:03:36 cs02 mfschunkserver[22075]: hdd_io_begin:
> file:/mnt/chunks/chunk0/chunk//01/chunk_00000000006639E9_00000001.mfs
> - read error: Success (errno=0)
> 
> But file /mnt/chunks/chunk0/chunk//01/chunk_00000000006639E9_00000001.mfs
> doesn't exist anymore.
> In case of crc mismatch, MooseFS will create a new chunk with a
> different file name ?

Number is the same, but version can be higher.
File name pattern is "chunk_UNIQUENUMBEROFCHUNK_VERSION.mfs"
UNIQUENUMBEROFCHUNK should be the same, but VERSION can be different.

> Is normal that with standard configuration, the crc mismatch is
> resolved after about 10 hours from discovery ?

If there is lot of other things to do (replication of other undergoal chunks for example) then yes. Such chunk should be treated in the same way as any other undergoal chunk. Did you check the GOAL/VC table on the Info tab in mfs.cgi? Did you have "yellow" chunks? If not then maybe system created valid copy, but didn't remove damaged chunk.



-- 
Regards,
Jakub Kruszona-Zawadzki
- - - - - - - - - - - - - - - -
Segmentation fault (core dumped)
Phone: +48 602 212 039