From: Michal B. <mic...@ge...> - 2011-06-01 09:30:31
|
Hi! We run several instances of MooseFS over 5 years already and have never seen an error like yours. There was a situation that one file was lacking and the other existing but without relation to anything. We added -i (ignore) flag to the mfsmetarestore and got this result: loading objects (files,directories,etc.) ... ok loading names ... loading edge: 7527,DSC01862.JPG->7554 error: child not found ok loading deletion timestamps ... ok checking filesystem consistency ... fschk: found lost inode: 7538 ok loading chunks data ... ok connecting files and chunks ... ok store metadata into file: ../../../Downloads/mfs/metadata.mfs Numbers of files differ exactly by one bit: >>> "%02X" % 7554 '1D82' >>> "%02X" % 7538 '1D72' We think that this problem could be caused by your RAM in the master. We recommend using RAM with parity control. You can also run a test from http://www.memtest.org/ on your server and check your existing RAM. Of course, the bit could have been changed also on the motherboard level or CPU - which is much less probable. Also you can see in the log that file 7538 is located between 7553 and 7555: -|i: 7549|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302156861,m:1088897360,c:1302340549|t: 86400|l: 978749|c:(0000000000001B1B)|r:() -|i: 7550|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302156866,m:1088897400,c:1302340549|t: 86400|l: 804362|c:(0000000000001B1C)|r:() -|i: 7551|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302156869,m:1088897438,c:1302340549|t: 86400|l: 850289|c:(0000000000001B1D)|r:() -|i: 7552|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302156873,m:1088897474,c:1302340549|t: 86400|l: 710445|c:(0000000000001B1E)|r:() -|i: 7553|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302156876,m:1098246428,c:1302340549|t: 86400|l: 456633|c:(0000000000001B1F)|r:() -|i: 7538|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302154827,m:1088893918,c:1302340549|t: 86400|l: 848797|c:(0000000000001B10)|r:() -|i: 7555|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302156878,m:1088897534,c:1302340549|t: 86400|l: 137858|c:(0000000000001B21)|r:() -|i: 7556|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302156878,m:1088898128,c:1302340549|t: 86400|l: 805701|c:(0000000000001B22)|r:() -|i: 7557|#:2|e:0|m:0777|u: 65534|g: 65534|a:1302156880,m:1088898148,c:1302340549|t: 86400|l: 817717|c:(0000000000001B23)|r:() -|i: 7558|#:2|e:0|m:0777|u: 65534|g: 65534|a:1157861440,m:1088898162,c:1302340549|t: 86400|l: 852298|c:(0000000000001B24)|r:() -|i: 7559|#:2|e:0|m:0777|u: 65534|g: 65534|a:1157861440,m:1088898186,c:1302340549|t: 86400|l: 797550|c:(0000000000001B25)|r:() -|i: 7560|#:2|e:0|m:0777|u: 65534|g: 65534|a:1157861440,m:1088898530,c:1302340549|t: 86400|l: 764878|c:(0000000000001B26)|r:() Kind regards -Michal -----Original Message----- From: Tuukka Luolamo [mailto:tlu...@gm...] Sent: Monday, May 30, 2011 7:40 PM To: Michal Borychowski Subject: Re: [Moosefs-users] Problems after power failure Hello Michael, Attached are the files you requested. Let me know if you need anything else. Now getting the meta files fixed would be great, but also if there is a way to rebuild them from the chunk servers contents that would be a viable option for this system as I only have two servers in the cluster, one acting as the master and a chunkserver and the other acting as the metalogger and a second chunk server. I have the replication set to 2 so both have all the contents of the file system. Also when it went down I am pretty sure there was nothing being written to the servers. This is my home / test system so getting the data back is important, but the time it takes to recover it is not. Thanks, Tuukka 2011/5/30 Michal Borychowski <mic...@ge...>: > Hi! > > If you could send us your "metadata.mfs*" and "changelog*" files > (tar.gzipped) - we'll see what can be done about it. > > > 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 > > > > -----Original Message----- > From: Tuukka Luolamo [mailto:tlu...@gm...] > Sent: Sunday, May 29, 2011 3:36 AM > To: moo...@li... > Subject: [Moosefs-users] Problems after power failure > > I had a power failure and both my master and meta logger went down > simultaneously. > > When I turned them back on the master process failed to start, so I > ran metarestore -a but got the following error: > > loading objects (files,directories,etc.) ... ok > loading names ... loading edge: 7527,DSC01862.JPG->7554 error: child not > found > error > can't read metadata from file: metadata.mfs.back > > So I went to the metalogger and got the same error. > > Now I am not sure what to try next. > > Any help would be appreciated. > > > Tuukka > > ---------------------------------------------------------------------------- > -- > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > > |