Re: [Moosefs-users] problem with mfsmetarestore.

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

Has the metalogger been restarted after downloading the metadata_ml.mfs.back
file? 

 

When you restore data on the metalogger machine you do not need master
server.

 

 

But please mind, that you cannot issue a command like this:

mfsmetarestore -m /data/mfs/meta/metadata_ml.mfs.back -o
/data/mfs/meta/metadata.mfs /data/mfs/meta/changelog_ml.*.mfs

 

As stated on the website I gave you below:

When you pass changelog filenames as parameters into the mfsmetarestore
command line tool, it is necessary to pass them in a chronological order. We
therefore recommend using mfsmetarestore -a which automatically will find
and apply the changelog files in their proper order.

 

So please just use "mfsmetarestore -a" on the metalogger machine.

 

If you still have problems you can send us the gzipped metadata files and we
will look into them why the problem can appear.

 

 

Regards

Michał 

 

 

From: Roast [mailto:zha...@gm...] 
Sent: Tuesday, August 10, 2010 10:58 AM
To: Michał Borychowski
Cc: moosefs-users
Subject: Re: [Moosefs-users] problem with mfsmetarestore.

 

Thanks Michał .

I want to restore the meta data from metalogger machine, so there is no
mfsdata.mfs.back  at the metalogger machine.

And at the metalogger server, metadata_ml.mfs.back will sync from master 24
hours as default, so I think we can restore the meta data with
metadata_ml.mfs.back and changelog_ml.0.mfs ~ changelog_ml.24.mfs. But we
met version mismatch and Data mismatch.

Here is some new logs.

----------------------------------------------------------------------------
-------------------------------------------
version after applying changelog: 2072593
applying changes from file: /usr/local/mfs/var/mfs/changelog_ml.1.mfs
meta data version: 2072593
version after applying changelog: 2077544
applying changes from file: /usr/local/mfs/var/mfs/changelog_ml.0.mfs
meta data version: 2077544
2081473: error: 32 (Data mismatch)
----------------------------------------------------------------------------
-------------------------------------------

And can you tell me how to fix this problem?  Or how to restore the metadata
without master?

Thanks again.



2010/8/10 Michał Borychowski <mic...@ge...>

Normally you do not run the master process on the metalogger machine. You do
it only when the main master server breaks down. In this situation you stop
metalogger, do metarestore and run the master process.

 

You do not need to do anything special to generate metadata_ml.mfs.back on
the metalogger machine. It will be just created. 

 

See http://www.moosefs.org/news-reader/items/metadata-ins-and-outs.html and
read about recovering metadata by mfsmetarestore. Generally you would need
to run "mfsmetarestore -a".

 

 

Regards

Michał 

 

From: Roast [mailto:zha...@gm...] 
Sent: Thursday, July 29, 2010 4:11 AM
To: moosefs-users
Subject: [Moosefs-users] problem with mfsmetarestore.

 

Hi,all.

I want to setup the metalogger server as the backup for the master, so I use
mfsmetarestore to generate the metadata.mfs to start the master at the
metalogger server. But it doesn't works.

Here is some logs:

----------------------------------------------------------------------------
-------------------------------------------
[root@localhost ~]# /usr/local/mfs/sbin/mfsmetarestore -m
/data/mfs/meta/metadata_ml.mfs.back -o /data/mfs/meta/metadata.mfs
/data/mfs/meta/changelog_ml.*.mfs
loading objects (files,directories,etc.) ... ok
loading names ... ok
loading deletion timestamps ... ok
checking filesystem consistency ... ok
loading chunks data ... ok
connecting files and chunks ... ok
applying changes from file: /data/mfs/meta/changelog_ml.0.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.10.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.11.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.12.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.13.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.14.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.15.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.16.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.17.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.18.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.19.mfs
meta data version: 961564
version after applying changelog: 961564
applying changes from file: /data/mfs/meta/changelog_ml.1.mfs
meta data version: 961564
963911: version mismatch
[root@localhost ~]# 
----------------------------------------------------------------------------
-------------------------------------------

version mismatch? How to fix this problem?

Thanks.

-- 
The time you enjoy wasting is not wasted time!




-- 
The time you enjoy wasting is not wasted time!