NameNode throws FileNotFoundException: Parent path does not exist on startup
----------------------------------------------------------------------------
Key: HADOOP-745
URL: http://issues.apache.org/jira/browse/HADOOP-745
Project: Hadoop
Issue Type: Bug
Components: dfs
Affects Versions: 0.8.0
Reporter: Nigel Daley
(with credit to Christian)
The following exception is reported by the namenode upon startup:
2006-11-22 12:18:17,713 ERROR org.apache.hadoop.dfs.NameNode:
java.io.FileNotFoundException: Parent path does not exist: /foo/bar
at org.apache.hadoop.dfs.FSDirectory$INode.addNode(FSDirectory.java:186)
at
org.apache.hadoop.dfs.FSDirectory.unprotectedMkdir(FSDirectory.java:731)
at org.apache.hadoop.dfs.FSEditLog.loadFSEdits(FSEditLog.java:254)
at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:191)
at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:321)
at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:230)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:145)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:137)
at org.apache.hadoop.dfs.NameNode.main(NameNode.java:585)
Perhaps the 'mkdirs' section
INode inserted = unprotectedMkdir(cur);
if (inserted != null) {
NameNode.stateChangeLog.debug("DIR* FSDirectory.mkdirs: "
+"created directory "+cur );
fsImage.getEditLog().logMkDir( inserted );
needs to be synchronized or the unprotectedMkdir method needs to be changed
to allow creating missing parent directories.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
