Re: [Moosefs-users] mfsmetarestore failure

[Ken <ken...@gm...>]

This situation *maybe* cause by mfsmetalogger still open changelog file(s).



On Sun, Sep 18, 2011 at 12:29 AM, Allen Landsidel <lan...@gm...
> wrote:

> After a hardware failure test, mfsmetarestore is returning me an error
> that I can't quite get my head around or figure out how to recover from.
>
> There is/was no metalogger yet, as this is an evaluation install on a
> single machine.
>
> The output of mfsmetarestore is:
>
> # mfsmetarestore -a
> 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
> 2642207: ',' expected
> 2642207: error: 1 (Operation not permitted)
>
> I'm unsure how to proceed.
>
> The metadata.mfs.back file exists.  There are also changelog files
> (changelog.N.mfs) where N is (0-6, 14-16).  7-13 are not there / missing.
>
> Any advice on how to get the system back online (without just purging
> all the data) would be appreciated!
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>