Re: [Moosefs-users] master shutdown unexpected

[Michał B. <mic...@ge...>]

Hi!

 

The situtation you describe should not have taken place as overwriting metadata.mfs.back with metadata.mfs.back.tmp should be an atomic operation in the file system. So theoretically the file metadata.mfs.back should be a proper metada file and metadata.mfs.back.tmp can contain partial data. First, you should take metadata.mfs.back and later metadata.mfs.back.tmp. If for some reason metadata.mfs.back is not accessible you should use metadata.mfs.back from a backup or metalogger machine and lastly you use metadata.mfs.back.tmp

 

 

Kind regards

Michał Borychowski 

MooseFS Support Manager

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Gemius S.A.

ul. Wołoska 7, 02-672 Warszawa

Budynek MARS, klatka D

Tel.: +4822 874-41-00

Fax : +4822 874-41-01

 

 

From: 欧阳晓华 [mailto:toa...@gm...] 
Sent: Sunday, September 12, 2010 7:01 AM
To: moo...@li...
Subject: [Moosefs-users] master shutdown unexpected

 

hello：

      my master server shutdown for lost power, when I start server again, I use mfsmetarestore -a to restore mfsdata,

it report that metadata.mfs.back can't be read, and I find var/mfs/metadata.mfs.back exist, but small than metadata.mfs.back.tmp

I copy metadata.mfs.back.tmp to metadata.mfs.back, mfsmetarestore runs OK.

I want to know if this action correct, is there any data lost? Or what can I do when master shutdown unexpected?

Thanks!