Hey Bradford, Your image is corrupt. Do you have an image from a second name.dir that has different md5sums?
It's sometimes possible to restore issues like this, but it usually requires using a tweaked namenode to skip over the bad data. -Todd On Tue, Jul 6, 2010 at 11:23 PM, Bradford Stephens < bradfordsteph...@gmail.com> wrote: > Hey guys, > > Running .20.2 -- namenode refuses to start. Ran fine the last few > weeks. Any ideas? > > Full text: http://pastebin.com/QWZ6A0Ja > 2010-07-06 23:20:01,524 ERROR > org.apache.hadoop.hdfs.server.namenode.NameNode: > java.lang.NullPointerException > at > org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1076) > at > org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1088) > at > org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedMkdir(FSDirectory.java:975) > at > org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedMkdir(FSDirectory.java:962) > > -- > Bradford Stephens, > Founder, Drawn to Scale > drawntoscalehq.com > 727.697.7528 > > http://www.drawntoscalehq.com -- The intuitive, cloud-scale data > solution. Process, store, query, search, and serve all your data. > > http://www.roadtofailure.com -- The Fringes of Scalability, Social > Media, and Computer Science > -- Todd Lipcon Software Engineer, Cloudera
