From: Gandalf C. <gan...@gm...> - 2018-06-14 10:40:41
|
Il giorno gio 14 giu 2018 alle ore 12:16 Jakub Kruszona-Zawadzki <jak...@ge...> ha scritto: > 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. No, there isn't any "new version". This is the error message I had: chunk_readcrc: file:/mnt/chunks/chunk0/chunk//01/chunk_00000000006639E9_00000001.mfs - read error: Success (errno=0) but /mnt/chunks/chunk0/chunk//01/chunk_00000000006639E9_00000001.mfs doesn't exist in any version. Probably it was replicated with a new chunk name # find /mnt/chunks/ -name 'chunk_00000000006639E9_*' # > 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. Honestly, i've not looked at CGI page because I was seeing in the log multipe "chunk_readcrc", thus, CRC mismatch was still detected. If CRC is detected, I think that MooseFS still haven't replicated (fixing the CRC) the chunk. This is a test cluster, no other operations where running. |