OK, I've just solved problem with minor data lost. Steps to solve:
1) comment out FSEditLog.java:542
2) compile hadoop-core jar
3) start cluster with new jar
Namenode will skip bad records in name/current/edits and write new edits
file back into fs. As bad records stand for actual IO operations,
Namenode fails to start and writes this error. What can I do to repair it?
2009-05-13 20:54:55,098 INFO namenode.FSNamesystem
(FSNamesystem.java:registerMBean(4464)) - Registered F
SNamesystemStatusMBean
2009-05-13 20:54:55,133 INFO common.Storage (FSImage.java:loadFSImage(852)) -
Number of
