From: Gandalf C. <gan...@gm...> - 2018-06-09 10:21:17
|
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 ? Is normal that with standard configuration, the crc mismatch is resolved after about 10 hours from discovery ? Il giorno ven 8 giu 2018 alle ore 15:45 Gandalf Corvotempesta <gan...@gm...> ha scritto: > > Il giorno ven 8 giu 2018 alle ore 15:44 Gandalf Corvotempesta > <gan...@gm...> ha scritto: > > is this OK ? The file was manually "rotted" by me, is normal that > > MooseFS detect corruption at 12:41:16 and did nothing until 15:34:25 ? > > 15:34 is also the same time I see in CGI, in last error field > > Correction: rotted chunk is still unrepaired. |