From: WK <wk...@bn...> - 2011-06-01 22:39:46
|
On 6/1/2011 2:30 AM, Michal Borychowski wrote: > > 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: So in a situation like this where the metadata is now corrupt. Is the problem fixable with only the loss of the one file? (and how does one fix it). or is his entire MFS setup completely corrupt and he would need to have had a backup? Can I assume that older archived versions of the metadata.mfs could be used to recover most of the files. -bill |