Re: [MooseFS-users] maintenance

[Piotr R. K. <pio...@mo...>]

Hello Eugene,
> 1) What maintenance mode does? What should happen when I switch it on or off?
It is described in "MooseFS User's Manual" - chapter 4.3. You can obtain it at http://moosefs.com/documentation.html[1].

> 2) Is there any way to force filesystem checks?
What do you mean exactly? The "filesystem check" loop is going all the time. When it ends, info is shown on CGI monitor and it starts over.

> 3) chunk is unavailable error. sometimes, after fs check I receive a 
> message, that the chunk is unavailable.
If you have missing chunk(s) in "All chunks state matrix", information about specific chunks/files missing is shown after filesystem check loop ends.

> currently unavailable chunk 000000000017EA9E (inode: 249094 ; index: 0)
> 
> I checked in fs structure and the chuck is really missed.
> How this could happen usually? If the file was written successfully, why it is missed now?
Do you have only unavailable chunk, or also *file*?

> Using latest stable CE edition. Linux, HDD fs is ext4.
Which version exactly? On Thursday, 22nd January 2015 we released MooseFS 2.0.48 as stable, please upgrade to 2.0.48.
Since 2.0.43 there were some fixes which may be important in you case (specifically regarding to missing chunks and *no unavailable files*). 


Can you send us some logs from master and this chunkserver, on which you have missing chunk from period you were writing files and the problem occured?

-- 
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer *| moosefs.com[2] 

On Sunday, January 25, 2015 12:10:11 PM Eugene Diatlov wrote:
> Hi everyone,
> 
> 1) What maintenance mode does? What should happen when I switch it on or 
> off?
> 
> 2) Is there any way to force filesystem checks?
> 
> 3) chunk is unavailable error. sometimes, after fs check I receive a 
> message, that the chunk is unavailable.
> 
> currently unavailable chunk 000000000017EA9E (inode: 249094 ; index: 0)
> 
> I checked in fs structure and the chuck is really missed.
> How this could happen usually? If the file was written successfully, why it is missed now?
> 
> Using latest stable CE edition. Linux, HDD fs is ext4.
> 
> 

--------
[1] http://moosefs.com/documentation.html
[2] http://moosefs.com