You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2011/07/14 21:56:00 UTC
[jira] [Resolved] (HADOOP-7458) Namenode not get started!
FSNamesystem initialization failed. java.io.FileNotFoundException
[ https://issues.apache.org/jira/browse/HADOOP-7458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Homan resolved HADOOP-7458.
---------------------------------
Resolution: Invalid
This appears to be an issue of file corruption. The best forum for resolving it is the mailing list, rather than the issue tracker. Please write to the hdfs users' list. Closing.
> Namenode not get started! FSNamesystem initialization failed. java.io.FileNotFoundException
> -------------------------------------------------------------------------------------------
>
> Key: HADOOP-7458
> URL: https://issues.apache.org/jira/browse/HADOOP-7458
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.20.2
> Environment: CentOS release 5.5 (Final), 18 node Cluster
> Reporter: Sakthivel Murugasamy
> Priority: Blocker
> Labels: hadoop
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> 2011-07-13 12:04:12,967 ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem initialization failed.
> java.io.FileNotFoundException: File does not exist: /opt/data/tmp/mapred/system/job_201107041958_0120/j^@^@^@^@^@^@
> at org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedSetPermission(FSDirectory.java:544)
> at org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:724)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(FSImage.java:992)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:812)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:364)
> at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:87)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:311)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:292)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:201)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:279)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:956)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:965)
> 2011-07-13 12:04:13,006 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: java.io.FileNotFoundException: File does not exist: /opt/data/tmp/mapred/system/job_201107041958_0120/j^@^@^@^@^@^@
> at org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedSetPermission(FSDirectory.java:544)
> at org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:724)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(FSImage.java:992)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:812)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:364)
> at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:87)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:311)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:292)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:201)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:279)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:956)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:965)
> In the path /opt/data/tmp/mapred, "system/" folder itself is not available
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira